From: Rik van Riel <riel@conectiva.com.br>
To: Andrew Morton <akpm@digeo.com>
Cc: Daniel Phillips <phillips@arcor.de>,
lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.34-mm2
Date: Sun, 15 Sep 2002 11:58:27 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44L.0209151156080.1857-100000@imladris.surriel.com> (raw)
In-Reply-To: <3D841C8A.682E6A5C@digeo.com>
On Sat, 14 Sep 2002, Andrew Morton wrote:
> Daniel Phillips wrote:
> > but that sure looks like the low hanging fruit.
>
> It's low alright. AFAIK Linux has always had this problem of
> seizing up when there's a lot of dirty data around.
Somehow I doubt the "seizing up" problem is caused by too much
scanning. In fact, I'm pretty convinced it is caused by having
too much IO submitted at once (and stalling in __get_request_wait).
The scanning is probably not relevant at all and it may be
beneficial to just ignore the scanning for now and do our best
to keep the pages in better LRU order.
regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
Spamtraps of the month: september@surriel.com trac@trac.org
next prev parent reply other threads:[~2002-09-15 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 6:29 2.5.34-mm2 Andrew Morton
2002-09-15 3:46 ` 2.5.34-mm2 Daniel Phillips
2002-09-15 4:12 ` 2.5.34-mm2 Andrew Morton
2002-09-15 4:23 ` 2.5.34-mm2 Daniel Phillips
2002-09-15 5:37 ` 2.5.34-mm2 Andrew Morton
2002-09-15 14:58 ` Rik van Riel [this message]
2002-09-15 17:13 ` 2.5.34-mm2 Andrew Morton
2002-09-15 17:08 ` 2.5.34-mm2 Daniel Phillips
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.0209151156080.1857-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=phillips@arcor.de \
/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).