linux-kernel - Re: [patch 6/7] cpusets: per cpuset dirty ratios

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, 29 Oct 2008 23:59:02 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"David Rientjes" <rientjes@...gle.com>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Christoph Lameter" <cl@...ux-foundation.org>,
	"Nick Piggin" <npiggin@...e.de>,
	"Peter Zijlstra" <peterz@...radead.org>,
	"Derek Fults" <dfults@....com>, linux-kernel@...r.kernel.org
Subject: Re: [patch 6/7] cpusets: per cpuset dirty ratios

On Tue, Oct 28, 2008 at 9:08 AM, David Rientjes <rientjes@...gle.com> wrote:
> From: Christoph Lameter <cl@...ux-foundation.org>
>
> This implements dirty ratios per cpuset.  Two new files are added to the
> cpuset directories:

Wouldn't this be equally applicable to cgroups using the memory
controller rather than cpusets? Might it make sense to have a common
subsystem that could be used by either of them?

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/