From: Christoph Lameter <clameter@sgi.com>
To: akpm@osdl.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Menage <menage@google.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-mm@kvack.org, Christoph Lameter <clameter@sgi.com>,
Paul Jackson <pj@sgi.com>, Dave Chinner <dgc@sgi.com>,
Andi Kleen <ak@suse.de>
Subject: [PATCH 0/5] Cpuset aware writeback V2
Date: Tue, 23 Jan 2007 10:52:43 -0800 (PST) [thread overview]
Message-ID: <20070123185242.2640.8367.sendpatchset@schroedinger.engr.sgi.com> (raw)
Currently cpusets are not able to do proper writeback since dirty ratio
calculations and writeback are all done for the system as a whole. This
may result in a large percentage of the nodes in a cpuset to become dirty
without background writeout being triggered and without synchrononous
writes occurring. Instead writeout occurs during reclaim when memory
is tight which may lead to dicey VM situations.
In order to fix the problem we first of all introduce a method to establish
a map of dirty nodes for each struct address_space.
Secondly, we modify the dirty limit calculation to be based on the current
state of memory on the nodes of the cpuset that the current tasks belongs to.
If the current tasks is part of a cpuset that is not allowed to allocate
from all nodes in the system then we select only inodes for writeback
that have pages on the nodes that we are allowed to allocate from.
Changelog: V1->V2
-----------------
- Remove stray diff chunk and general patch beautification
- Put do { } while (0) around cpuset_update_dirty_nodes macro since it
contains and if()
- Update comments to clarify locking scheme for dirty node maps.
- Retest and verify compile on UP.
Changelog: RFC->V1
------------------
- Rework dirty_map logic to allocate it dynamically on larger
NUMA systems. Move to struct address_space and address various minor issues.
- Dynamically allocate dirty maps only if an inode is dirtied.
- Clear the dirty map only when an inode is cleared (simplifies
locking and we need to keep the dirty state even after the dirty state of
all pages has be cleared for NFS writeout to occur correctly).
- Drop nr_node_ids patches
- Drop the NR_UNRECLAIMABLE patch. There may be other ideas around on how
to accomplish the same in a more elegant way.
- Drop mentioning the NFS issues since Peter is working on those.
--
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 reply other threads:[~2007-01-23 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 18:52 Christoph Lameter [this message]
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
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
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=20070123185242.2640.8367.sendpatchset@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 \
/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).