On Thu, Mar 01, 2007 at 10:31:26AM -0600, Serge E. Hallyn wrote: > we've already had some trouble with nsproxy holding things with > different lifetimes. As it happens the solution this time was to put > the pid namespace where it belongs - not in nsproxy - so maybe moving > this info into nsproxies will be fine, it just rings a warning bell.
nsproxy seems the best place to me to hang off the resource control objects (nsproxy->ctlr_data[]). These objects provide information like resource limit etc required by the resource controllers. Alternately we could move them to task_struct which would cause unnecessary duplication of pointers (and wastage of space). -- Regards, vatsa - 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/
