From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 19 Apr 2007 09:03:53 -0700 (PDT) From: Christoph Lameter Subject: Re: [RFC 0/8] Cpuset aware writeback In-Reply-To: <46271FB7.9030408@google.com> Message-ID: References: <20070116054743.15358.77287.sendpatchset@schroedinger.engr.sgi.com> <45C2960B.9070907@google.com> <46019F67.3010300@google.com> <4626CEDA.7050608@google.com> <46271FB7.9030408@google.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Ethan Solomita Cc: akpm@osdl.org, Paul Menage , linux-kernel@vger.kernel.org, Nick Piggin , linux-mm@kvack.org, Andi Kleen , Paul Jackson , Dave Chinner , KAMEZAWA Hiroyuki List-ID: On Thu, 19 Apr 2007, Ethan Solomita wrote: > > Hmmmm.... Sorry. I got distracted and I have sent them to Kame-san who was > > interested in working on them. > > I have placed the most recent version at > > http://ftp.kernel.org/pub/linux/kernel/people/christoph/cpuset_dirty > > > > Do you expect any conflicts with the per-bdi dirty throttling patches? You would have to check that yourself. The need for cpuset aware writeback is less due to writeback fixes to NFS. The per bdi dirty throttling is further reducing the need. The role of the cpuset aware writeback is simply to implement measures to deal with the worst case scenarios. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org