From: Andrew Morton <akpm@zip.com.au>
To: Rik van Riel <riel@conectiva.com.br>
Cc: William Lee Irwin III <wli@holomorphy.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] adjustments to dirty memory thresholds
Date: Wed, 28 Aug 2002 19:10:43 -0700 [thread overview]
Message-ID: <3D6D82A3.A3A0C7F0@zip.com.au> (raw)
In-Reply-To: Pine.LNX.4.44L.0208282124550.1857-100000@imladris.surriel.com
Rik van Riel wrote:
>
> On Wed, 28 Aug 2002, Andrew Morton wrote:
>
> > But sigh. Pointlessly scanning zillions of dirty pages and doing
> > nothing with them is dumb. So much better to go for a FIFO snooze on a
> > per-zone waitqueue, be woken when some memory has been cleansed.
>
> But not per-zone, since many (most?) allocations can be satisfied
> from multiple zones. Guess what 2.4-rmap has had for ages ?
Per-classzone ;)
> Interested in a port for 2.5 on top of 2.5.32-mm2 ? ;)
>
> [I'll mercilessly increase your patch queue since it doesn't show
> any sign of ever shrinking anyway]
Lack of patches is not a huge problem at present ;). It's getting them
tested for performance, stability and general does-good-thingsness
which is the rate limiting step.
The next really significant design change in the queue is slablru,
and we'll need to let that sit in partial isolation for a while to
make sure that it's doing what we want it to do.
But yes, I'm interested in a port of the code, and in the description
of the problems which it solves, and how it solves them. But what is
even more valuable than the code is a report of its before-and-after
effectiveness under a broad range of loads on a broad range of
hardware. That's the most time-consuming part...
next prev parent reply other threads:[~2002-08-29 1:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 4:39 [patch] adjustments to dirty memory thresholds Andrew Morton
2002-08-28 20:08 ` William Lee Irwin III
2002-08-28 20:27 ` Andrew Morton
2002-08-28 21:42 ` William Lee Irwin III
2002-08-28 21:58 ` Andrew Morton
2002-08-28 22:15 ` Andrew Morton
2002-08-29 0:26 ` Rik van Riel
2002-08-29 2:10 ` Andrew Morton [this message]
2002-08-29 2:10 ` Rik van Riel
2002-08-29 2:52 ` Andrew Morton
2002-09-01 1:37 ` William Lee Irwin III
2002-08-29 3:49 ` William Lee Irwin III
2002-08-29 12:37 ` Rik van Riel
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=3D6D82A3.A3A0C7F0@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=wli@holomorphy.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).