linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@google.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Ethan Solomita <solo@google.com>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
	a.p.zijlstra@chello.nl
Subject: Re: [RFC 1/7] cpuset write dirty map
Date: Wed, 27 Jun 2007 02:14:08 -0700	[thread overview]
Message-ID: <20070627021408.493812fe.akpm@google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706262017260.24504@schroedinger.engr.sgi.com>

On Tue, 26 Jun 2007 20:18:36 -0700 (PDT) Christoph Lameter <clameter@sgi.com> wrote:

> On Tue, 26 Jun 2007, Andrew Morton wrote:
> 
> > Is in my queue somewhere.  Could be that by the time I get to it it will
> > need refreshing (again), we'll see.
> > 
> > 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. 
> > Having a 100:1 coder:reviewer ratio doesn't exactly make for swift
> > progress.
> 
> Hmmmm.. How can we help? I can look at some aspects of Peter's per device 
> throttling.

That can't hurt.

I'm more concerned about all of Mel's code in -mm actually.  I don't recall
anyone doing a full review recently and I'm still not sure that this is the
overall direction in which we wish to go.  Last time I asked this everyone
seemed a bit waffly and non-committal.



  reply	other threads:[~2007-06-27  9:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01  6:03 [RFC 1/7] cpuset write dirty map Ethan Solomita
2007-06-01  6:10 ` [RFC 2/7] cpuset write pdflush nodemask Ethan Solomita
2007-06-01  6:11 ` [RFC 3/7] cpuset write throttle Ethan Solomita
2007-06-01  6:13 ` [RFC 4/7] cpuset write vmscan Ethan Solomita
2007-06-01  6:15 ` [RFC 5/7] cpuset write vm writeout Ethan Solomita
2007-06-01  6:16 ` [corrected][RFC " Ethan Solomita
2007-06-01  6:16 ` [RFC 6/7] cpuset write fixes Ethan Solomita
2007-06-01  6:17 ` [RFC 7/7] cpuset dirty limits Ethan Solomita
2007-06-04 18:39 ` [RFC 1/7] cpuset write dirty map Christoph Lameter
2007-06-04 19:38   ` Ethan Solomita
2007-06-04 19:52     ` Christoph Lameter
2007-06-25 20:21       ` Ethan Solomita
2007-06-26 19:16         ` Christoph Lameter
2007-06-26 22:22           ` Andrew Morton
2007-06-27  3:18             ` Christoph Lameter
2007-06-27  9:14               ` Andrew Morton [this message]
2007-06-27 12:44                 ` Christoph Lameter
2007-06-27 21:10                   ` Mel Gorman
2007-06-27 18:17             ` Ethan Solomita
2007-06-27 21:38               ` Christoph Lameter
2007-07-01  2:57                 ` Ethan Solomita
2007-07-03 18:09                   ` Christoph Lameter
2007-07-11 19:18           ` Ethan Solomita
2007-07-11 20:11             ` Christoph Lameter
2007-07-12  1:07               ` Ethan Solomita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070627021408.493812fe.akpm@google.com \
    --to=akpm@google.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=solo@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).