Quoting Paul Menage (menage@xxxxxxxxxx): > On 6/8/07, Serge E. Hallyn <serge@xxxxxxxxxx> wrote: > > > >Anyway the patch I sent is simple enough, and if users end up demanding > >the ability to better deal with exclusive cpusets, the patch will be > >simple enough to extend by changing cpuset_auto_setup(), so let's > >stick with that patch since it's your preference (IIUC). > > > > Sounds good to me, although I think my preference would be to extend > the "create()" subsystem callback with a "struct task_struct > *clone_task" parameter that indicates that clone_task is cloning its > own container; a subsystem like cpusets that needs to do additional > setup at that point could inherit settings either from the parent or > from clone_task's container (or something else) as desired. (It could > also do permission checking based on properties of clone_task, etc). The problem is container_clone() doesn't call ->create explicitly, it does vfs_mkdir. So we have no real way of passing in clone_task. -serge _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
