From: Rik van Riel <riel@conectiva.com.br>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Andrew Morton <akpm@zip.com.au>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: throttling dirtiers
Date: Wed, 31 Jul 2002 17:26:27 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44L.0207311725530.23404-100000@imladris.surriel.com> (raw)
In-Reply-To: <20020731162357.Q10270@redhat.com>
On Wed, 31 Jul 2002, Benjamin LaHaise wrote:
> Why? Filling the entire ram with dirty pages is okay, and in fact you
> want to support that behaviour for apps that "just fit" (think big
> scientific apps). The only interesting point is that when you hit the
> limit of available memory, the system needs to block on *any* io
> completing and resulting in clean memory (which is reasonably low
> latency), not a specific io which may have very high latency.
Also, the system shouldn't try writing out the complete inactive
list at once and blocking in __get_request_wait instead of grabbing
pages as they become cleaned.
regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
--
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/
next prev parent reply other threads:[~2002-07-31 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 8:26 Andrew Morton
2002-07-31 20:06 ` William Lee Irwin III
2002-07-31 20:23 ` Benjamin LaHaise
2002-07-31 20:26 ` Rik van Riel [this message]
2002-07-31 20:59 ` William Lee Irwin III
2002-07-31 21:02 ` Andrew Morton
2002-07-31 21:14 ` Benjamin LaHaise
2002-07-31 21:25 ` Rik van Riel
2002-07-31 21:32 ` Andrew Morton
2002-07-31 21:55 ` Rik van Riel
2002-07-31 22:24 ` Andrew Morton
2002-07-31 22:32 ` Rik van Riel
2002-07-31 21:28 ` Andrew Morton
2002-07-31 21:35 ` 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=Pine.LNX.4.44L.0207311725530.23404-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=akpm@zip.com.au \
--cc=bcrl@redhat.com \
--cc=linux-mm@kvack.org \
--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