From: Christoph Lameter <clameter@sgi.com>
To: Ethan Solomita <solo@google.com>
Cc: akpm@osdl.org, Paul Menage <menage@google.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-mm@kvack.org, Paul Jackson <pj@sgi.com>,
Dave Chinner <dgc@sgi.com>, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 1/5] Add a map to to track dirty pages per node
Date: Wed, 24 Jan 2007 21:52:09 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0701242143200.13327@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <45B81E5B.1090505@google.com>
On Wed, 24 Jan 2007, Ethan Solomita wrote:
> The below addition makes us skip inodes outside of our dirty nodes. Do we
> want this even with WB_SYNC_ALL and WB_SYNC_HOLD? It seems that callers from
> sync_inodes_sb(), which are the ones that pass in those options, may want to
> know that everything is written.
A constraint on the nodes requires setting wbc.nodes. I could not find a
writeback_control setup that uses either of those flags and also sets
wbc.nodes.
And WB_SYNC_ALL is already used with another constraints on a
mapping to only partially sync.
If a caller in the future sets wbc.nodes plus either of those options then
it is an attempt to perform these operations only on a subset of nodes.
--
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>
next prev parent reply other threads:[~2007-01-25 5:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 18:52 [PATCH 0/5] Cpuset aware writeback V2 Christoph Lameter
2007-01-23 18:52 ` [PATCH 1/5] Add a map to to track dirty pages per node Christoph Lameter
2007-01-25 3:04 ` Ethan Solomita
2007-01-25 5:52 ` Christoph Lameter [this message]
2007-01-23 18:52 ` [PATCH 2/5] Add a nodemask to pdflush functions Christoph Lameter
2007-01-23 18:52 ` [PATCH 3/5] Per cpuset dirty ratio calculation Christoph Lameter
2007-01-23 18:53 ` [PATCH 4/5] Cpuset aware writeback during reclaim Christoph Lameter
2007-01-23 18:53 ` [PATCH 5/5] Throttle vm writeout per cpuset Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2007-01-20 3:10 [PATCH 0/5] Cpuset aware writeback V1 Christoph Lameter
2007-01-20 3:10 ` [PATCH 1/5] Add a map to to track dirty pages per node Christoph Lameter
2007-01-20 5:15 ` Paul Jackson
2007-01-22 17:41 ` Christoph Lameter
2007-01-22 1:31 ` David Chinner
2007-01-22 19:30 ` Christoph Lameter
2007-01-28 21:38 ` David Chinner
2007-01-29 16:50 ` Christoph Lameter
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=Pine.LNX.4.64.0701242143200.13327@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--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).