Messages in this thread | | | Subject | Re: sysctls inside containers | From | (Eric W. Biederman) | Date | Fri, 10 Mar 2006 04:55:34 -0700 |
| |
Kirill Korotaev <dev@sw.ru> writes:
>> 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...
Yes, netlink is something to be considered in the great untangling.
However for a sysvipc namespace ipc/mqueue.c is something that doesn't need to be handled because that is the implementation of posix message queues not sysv ipc.
I think I succeeded in untagling the worst of netlink in my proof of concept implementation, but certainly there is more todo.
Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |