linux-kernel - Re: [patch 0/7] cpuset writeback throttling

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: <alpine.DEB.2.00.0811041306510.27392@chino.kir.corp.google.com>
Date:	Tue, 4 Nov 2008 13:10:57 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>, cl@...ux-foundation.org,
	npiggin@...e.de, menage@...gle.com, dfults@....com,
	linux-kernel@...r.kernel.org
Subject: Re: [patch 0/7] cpuset writeback throttling

On Tue, 4 Nov 2008, Peter Zijlstra wrote:

> I think the main reason is that we have per-node vmstats so the cpuset
> extention is relatively easy. Whereas we do not currently maintain
> vmstats on a cgroup level - although I imagine that could be remedied.
> 

That's correct, the ZVC values from each node assigned to a particular 
cpuset is used to determine the dirty ratios.  We don't currently have the 
infrastructure to do that with any other cgroup.

So extracting this out to a separate cgroup is fine, but it's still only 
applicable to cpusets at this time.  Let me know what the prerequisites 
are for -mm inclusion.
--
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/