On Wed, Mar 07, 2007 at 04:16:00PM -0700, Eric W. Biederman wrote: > I think implementation wise this tends to make sense. > However it should have nothing to do with semantics. > > If we have a lot of independent resource controllers. Placing the > pointer to their data structures directly in nsproxy instead of in > task_struct sounds like a reasonable idea
Thats what the rcfs patches do. > but it should not be user visible. What do you mean by this? We do want the user to be able to manipulate the resource parameters (which are normally present in the data structures/resource objects pointed to by nsproxy - nsproxy->ctlr_data[]) -- 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/
