linux-kernel - Re: [PATCH 0/2] CGroups: cgroup member list enhancement/fix

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6599ad830907130926v7788af12hdcd76e4ccb3ab6de@mail.gmail.com>
Date:	Mon, 13 Jul 2009 09:26:26 -0700
From:	Paul Menage <menage@...gle.com>
To:	balbir@...ux.vnet.ibm.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

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.

Paul
--
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/