Re: sysctls inside containers

On another note, after messing with putting data in the init_task for
these things, I'm a little more convinced that we aren't going to want
to clutter up the task_struct with all kinds of containerized resources,
_plus_ make all of the interfaces to share or unshare each of those.
That global 'struct container' is looking a bit more attractive.

BTW, Dave,

have you noticed that ipc/mqueue.c uses netlink to send messages?
This essentially means that they are tied as well...

Thanks,
Kirill

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: sysctls inside containers
    • From: Dave Hansen <[email protected]>
  • Re: sysctls inside containers
    • From: [email protected] (Eric W. Biederman)

• References:
  • Which of the virtualization approaches is more suitable for kernel?
    • From: Kirill Korotaev <[email protected]>
  • Re: Which of the virtualization approaches is more suitable for kernel?
    • From: [email protected] (Eric W. Biederman)
  • Re: Which of the virtualization approaches is more suitable for kernel?
    • From: Dave Hansen <[email protected]>
  • Re: Which of the virtualization approaches is more suitable for kernel?
    • From: [email protected] (Eric W. Biederman)
  • sysctls inside containers
    • From: Dave Hansen <[email protected]>

• Prev by Date: Re: sysctls inside containers
• Next by Date: Re: How can I link the kernel with libgcc ?
• Previous by thread: Re: sysctls inside containers
• Next by thread: Re: sysctls inside containers
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]