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]

Date:	Wed, 20 Sep 2006 14:04:01 -0700
From:	Paul Jackson <pj@....com>
To:	"Paul Menage" <menage@...gle.com>
Cc:	sekharan@...ibm.com, npiggin@...e.de,
	ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	rohitseth@...gle.com, devel@...nvz.org, clameter@....com
Subject: Re: [ckrm-tech] [patch00/05]: Containers(V2)- Introduction

Paul M. wrote:
> I'm not saying that they can - but they could be parallel types of
> resource controller for a generic container abstraction,

When there are a sufficiently large number of sufficiently
similar types of objects, such as for example file systems,
then a 'generic container abstraction' such as vfs in the
file system case becomes well worth it, even essential.

I'll be surprised if we have enough such similarity between
cpusets and resource groups to be able to find a useful abstract
generalization that is common to them both.

But if someone finds a way to rewrite resource groups using
cpusets and can convince the resource group folks of this,
I'm game to consider it.

Just because some abstract generalizations are good doesn't
mean they all are.

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