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-next>] [day] [month] [year] [list]
Date:	Wed, 20 Sep 2006 16:54:08 -0700
From:	Paul Jackson <pj@....com>
To:	"Paul Menage" <menage@...gle.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

Paul M. wrote:
> idea of separation between the container aspects of cpusets (which are
> almost identical to the container aspects of resource groups) and the
> resource control portions. Essentially, I've
> 
> - ripped out the cpusetfs portions of cpusets and moved them to container.c

There may be an opportunity here, I agree.  Sorry for not realizing
what you were getting at before.

I might not have time to study the details of this yet, and may wait
until it is a bit clearer to me which other resource/container/grouping
thingies are closer to final acceptance, but there are a few neurons
off in one corner of my brain that have long suspected that a single
chunk of kernel pseudo file system code, layered on vfs, should serve
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.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
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