linux-kernel - Re: [ckrm-tech] [patch00/05]: Containers(V2)- Introduction

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: <6599ad830609201657h1756d28eh4a04f85467f30ed2@mail.google.com>
Date:	Wed, 20 Sep 2006 16:57:48 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Paul Jackson" <pj@....com>
Cc:	npiggin@...e.de, sekharan@...ibm.com,
	ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	rohitseth@...gle.com, clameter@....com
Subject: Re: [ckrm-tech] [patch00/05]: Containers(V2)- Introduction

On 9/20/06, Paul Jackson <pj@....com> wrote:
> these various mechanisms, including cpusets.  It would be good to
> persue this common technology infrastructure -before- the kernel to
> user API of these other thingies gets frozen, as the details of just
> what this common code can do conveniently might impact details of the
> kernel API presented to users.

Indeed - although one of the advantages of the patch I sent is that it
can continue to present exactly the same interface, and functionality,
to userspace as the current cpusets code does. It wouldn't be
necessary to change the userspace API until the "generic" requirements
were more baked.

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/