[PATCH 0/2] resource control file system - aka containers on top of nsproxy!

Eric W. Biederman ebiederm at xmission.com
Wed Mar 7 15:16:00 PST 2007


"Paul Menage" <menage at google.com> writes:

> No, Sam was saying that nsproxy should be the object that all resource
> controllers hook off.

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 but it should not be user
visible.

Eric



More information about the Containers mailing list