Re: [ckrm-tech] [PATCH 7/7] containers (V7): Container interface to nsproxy subsystem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/5/07, Pavel Emelianov <xemul@xxxxx> wrote:
> > That sort of implies that we need to split the container fork
> > mechanism up into two parts, one early to add the refcount to the
> > parent's container_group, and one late to handle the callbacks if
> > desired. But that should be pretty straightforward.
>
> Splitting sounds good. I'll try to prepare an appropriate patch.

I just did this in my tree. It's a pretty simple patch, but it's a bit ugly.

> >> 2. early need for rss containers (earlier than initcalls
> >>    are called)
> >
> > Couldn't you copy the way cpuset_init_early() works?
>
> I did this in my previous version of rss container,
> but I think it can be generalized. This is initialization
> code that must not be nice-looking, but if it can be it
> should be.
>

Agreed, nice looking code is better :-)

Did you have any suggestions, other than moving container_init()
earlier in the boot process?

Paul
_______________________________________________
Containers mailing list
Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/containers


[Index of Archives]     [Cgroups]     [Netdev]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux