linux-kernel - Re: [RFC 1/7] cpuset write dirty map

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: <4682A9B6.8070003@google.com>
Date:	Wed, 27 Jun 2007 14:17:26 -0400
From:	Ethan Solomita <solo@...gle.com>
To:	Andrew Morton <akpm@...gle.com>
CC:	Christoph Lameter <clameter@....com>, linux-mm@...ck.org,
	LKML <linux-kernel@...r.kernel.org>, a.p.zijlstra@...llo.nl
Subject: Re: [RFC 1/7] cpuset write dirty map

Andrew Morton wrote:
> 
> One open question is the interaction between these changes and with Peter's
> per-device-dirty-throttling changes.  They also are in my queue somewhere. 

	I looked over it at one point. Most of the code doesn't conflict, but I
believe that the code path which calculates the dirty limits will need
some merging. Doable but non-trivial.
	-- Ethan
-
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/