From: Rik van Riel <riel@redhat.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@suse.de>,
Rohit Seth <rohitseth@google.com>, Andrew Morton <akpm@osdl.org>,
mbligh@google.com, hugh@veritas.com, andrea@suse.de,
arjan@infradead.org, apw@shadowen.org, mel@csn.ul.ie,
marcelo@kvack.org, anton@samba.org, paulmck@us.ibm.com,
Nick Piggin <piggin@cyberone.com.au>,
linux-mm <linux-mm@kvack.org>,
Nikita Danilov <nikita@clusterfs.com>
Subject: Re: [RFC][PATCH] inactive_clean
Date: Mon, 19 Jun 2006 15:27:04 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606191526401.6565@cuia.boston.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606191223410.3925@schroedinger.engr.sgi.com>
On Mon, 19 Jun 2006, Christoph Lameter wrote:
> On Mon, 19 Jun 2006, Rik van Riel wrote:
>
> > Not only swap. Writable MAP_SHARED mmap has the same problem...
>
> Writable MAP_SHARED is throttled by Peter Z. other patchset on page
> dirtying. So the problem should have been solved at that level.
This new patch throttles both. It might even make the other
one less needed - not sure...
--
All Rights Reversed
--
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:[~2006-06-19 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 12:20 Peter Zijlstra
2006-06-19 15:45 ` Christoph Lameter
2006-06-19 18:10 ` Peter Zijlstra
2006-06-19 19:03 ` Christoph Lameter
2006-06-19 19:10 ` Rik van Riel
2006-06-19 19:24 ` Christoph Lameter
2006-06-19 19:27 ` Rik van Riel [this message]
2006-06-19 19:58 ` Christoph Lameter
2006-06-19 20:05 ` Peter Zijlstra
2006-06-19 20:11 ` Christoph Lameter
2006-06-19 20:46 ` Peter Zijlstra
2006-06-19 21:48 ` Christoph Lameter
2006-06-19 20:28 ` Rik van Riel
2006-06-19 21:45 ` 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.0606191526401.6565@cuia.boston.redhat.com \
--to=riel@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=anton@samba.org \
--cc=apw@shadowen.org \
--cc=arjan@infradead.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.org \
--cc=mbligh@google.com \
--cc=mel@csn.ul.ie \
--cc=nikita@clusterfs.com \
--cc=paulmck@us.ibm.com \
--cc=piggin@cyberone.com.au \
--cc=rohitseth@google.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox