linux-kernel - Re: [RFC][PATCH 0/4] Generic container system

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: <6599ad830610041442t14b627bbs7b37c98b1e10852c@mail.gmail.com>
Date:	Wed, 4 Oct 2006 14:42:39 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	sekharan@...ibm.com
Cc:	"Martin Bligh" <mbligh@...gle.com>, pj@....com, akpm@...l.org,
	ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	winget@...gle.com, rohitseth@...gle.com, jlan@....com,
	Joel.Becker@...cle.com, Simon.Derr@...l.net
Subject: Re: [RFC][PATCH 0/4] Generic container system

On 10/4/06, Chandra Seetharaman <sekharan@...ibm.com> wrote:
> > All of this (and the rest of the snipped email with suggested
> > improvements) makes pretty good sense. But would it not be better
> > to do this in stages?
> >
> > 1) Split the code out from cpusets
>
> Paul (Menage) is already work on this.

The split out is done - right now I'm tidying up an example of RG
moved over the container API - basically dumping the group membership
code (since container.c supplies that) and migrating the shares/stats
file model to containerfs rather than configfs. I'll try to send it
out today.

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/