linux-kernel - Re: [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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 20 Sep 2006 09:48:13 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Nick Piggin <npiggin@...e.de>
cc:	Rohit Seth <rohitseth@...gle.com>,
	CKRM-Tech <ckrm-tech@...ts.sourceforge.net>, devel@...nvz.org,
	pj@....com, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch00/05]: Containers(V2)- Introduction

On Wed, 20 Sep 2006, Nick Piggin wrote:

> > Right thats what cpusets do and it has been working fine for years. Maybe 
> > Paul can help you if you find anything missing in the existing means to 
> > control resources.
> 
> What I like about Rohit's patches is the page tracking stuff which 
> seems quite simple but capable.
> 
> I suspect cpusets don't quite provide enough features for non-exclusive 
> use of memory (eg. page tracking for directed reclaim).

Look at the VM statistics please. We have detailed page statistics per 
zone these days. If there is anything missing then this would best be put 
into general functionality. When I looked at it, I saw page statistics 
that were replicating things that we already track per zone. All these 
would become available if a container is realized via a node and we would 
be using proven VM code.


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