"Paul Menage" <menage@xxxxxxxxxx> 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 _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxx https://lists.osdl.org/mailman/listinfo/containers
