* menage@xxxxxxxxxx <menage@xxxxxxxxxx> [2009-07-13 09:26:26]: > On Mon, Jul 13, 2009 at 5:11 AM, Balbir Singh<balbir@xxxxxxxxxxxxxxxxxx> wrote: > > > > How about lazy migration? Mark a group as to move when the kernel sees > > it next for scheduling. > > Waiting for the next scheduling point might be too long, since a > thread can block for arbitrary amounts of time and keeping the marker > around for arbitrary time (unless we add a new task_struct field) > would be tricky. Marking the cgroup or tgid as being migrated which > then triggers the extra synchronization in the fork path (but which > isn't needed at other times) is probably where we'll end up. Hmm... but we would not need that information till we schedule the tasks, adding a field to task_struct is what I had in mind. -- Balbir _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
