| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090714055638.GI5051@balbir.in.ibm.com> Date: Tue, 14 Jul 2009 11:26:38 +0530 From: Balbir Singh <balbir@...ux.vnet.ibm.com> To: Paul Menage <menage@...gle.com> Cc: lizf@...fujitzu.com, bblum@...gle.com, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, containers@...ts.linux-foundation.org, libcg-devel <libcg-devel@...ts.sourceforge.net> Subject: Re: [PATCH 0/2] CGroups: cgroup member list enhancement/fix * menage@...gle.com <menage@...gle.com> [2009-07-13 09:26:26]: > On Mon, Jul 13, 2009 at 5:11 AM, Balbir Singh<balbir@...ux.vnet.ibm.com> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists