All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ethan Solomita <solo@google.com>
To: Andrew Morton <akpm@google.com>
Cc: Christoph Lameter <clameter@sgi.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 14:17:26 -0400	[thread overview]
Message-ID: <4682A9B6.8070003@google.com> (raw)
In-Reply-To: <20070626152204.b6b4bc3f.akpm@google.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Ethan Solomita <solo@google.com>
To: Andrew Morton <akpm@google.com>
Cc: Christoph Lameter <clameter@sgi.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 14:17:26 -0400	[thread overview]
Message-ID: <4682A9B6.8070003@google.com> (raw)
In-Reply-To: <20070626152204.b6b4bc3f.akpm@google.com>

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, 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2007-06-27 18:18 UTC|newest]

Thread overview: 51+ 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:03 ` Ethan Solomita
2007-06-01  6:10 ` [RFC 2/7] cpuset write pdflush nodemask Ethan Solomita
2007-06-01  6:10   ` Ethan Solomita
2007-06-01  6:11 ` [RFC 3/7] cpuset write throttle Ethan Solomita
2007-06-01  6:11   ` Ethan Solomita
2007-06-01  6:13 ` [RFC 4/7] cpuset write vmscan Ethan Solomita
2007-06-01  6:13   ` Ethan Solomita
2007-06-01  6:15 ` [RFC 5/7] cpuset write vm writeout Ethan Solomita
2007-06-01  6:15   ` Ethan Solomita
2007-06-01  6:16 ` [corrected][RFC " Ethan Solomita
2007-06-01  6:16   ` Ethan Solomita
2007-06-01  6:16 ` [RFC 6/7] cpuset write fixes Ethan Solomita
2007-06-01  6:16   ` Ethan Solomita
2007-06-01  6:17 ` [RFC 7/7] cpuset dirty limits Ethan Solomita
2007-06-01  6:17   ` Ethan Solomita
2007-06-04 18:39 ` [RFC 1/7] cpuset write dirty map Christoph Lameter
2007-06-04 18:39   ` Christoph Lameter
2007-06-04 19:38   ` Ethan Solomita
2007-06-04 19:38     ` Ethan Solomita
2007-06-04 19:52     ` Christoph Lameter
2007-06-04 19:52       ` Christoph Lameter
2007-06-25 20:21       ` Ethan Solomita
2007-06-25 20:21         ` Ethan Solomita
2007-06-26 19:16         ` Christoph Lameter
2007-06-26 19:16           ` Christoph Lameter
2007-06-26 22:22           ` Andrew Morton
2007-06-26 22:22             ` Andrew Morton
2007-06-27  3:18             ` Christoph Lameter
2007-06-27  3:18               ` Christoph Lameter
2007-06-27  9:14               ` Andrew Morton
2007-06-27  9:14                 ` Andrew Morton
2007-06-27 12:44                 ` Christoph Lameter
2007-06-27 12:44                   ` Christoph Lameter
2007-06-27 21:10                   ` Mel Gorman
2007-06-27 21:10                     ` Mel Gorman
2007-06-27 18:17             ` Ethan Solomita [this message]
2007-06-27 18:17               ` Ethan Solomita
2007-06-27 21:38               ` Christoph Lameter
2007-06-27 21:38                 ` Christoph Lameter
2007-07-01  2:57                 ` Ethan Solomita
2007-07-01  2:57                   ` Ethan Solomita
2007-07-03 18:09                   ` Christoph Lameter
2007-07-03 18:09                     ` Christoph Lameter
2007-07-11 19:18           ` Ethan Solomita
2007-07-11 19:18             ` Ethan Solomita
2007-07-11 20:11             ` Christoph Lameter
2007-07-11 20:11               ` Christoph Lameter
2007-07-12  1:07               ` Ethan Solomita
2007-07-12  1:07                 ` Ethan Solomita
  -- strict thread matches above, loose matches on Subject: below --
2007-04-23 23:20 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=4682A9B6.8070003@google.com \
    --to=solo@google.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@google.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.