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

lists.openwall.net		lists / announce john-users owl-users popa3d-users / xvendor oss-security / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4
Open Source and information security mailing list archives

This website is powered by Openwall GNU/*/Linux security-enhanced OS

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

Date:	Sat, 30 Jun 2007 22:57:03 -0400
From:	Ethan Solomita <solo@...gle.com>
To:	Christoph Lameter <clameter@....com>
Subject: Re: [RFC 1/7] cpuset write dirty map

Christoph Lameter wrote:
> On Wed, 27 Jun 2007, Ethan Solomita wrote:
> 
>> 	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
> 
> I hope you will keep on updating the patchset and posting it against 
> current mm?
> 

	I have no new changes, but I can update it against the current mm. Or
did the per-bdi throttling change get taken by Andrew?
	-- 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/