From: Daniel Phillips <phillips@arcor.de>
To: Andrew Morton <akpm@digeo.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
William Lee Irwin III <wli@holomorphy.com>,
sfkaplan@cs.amherst.edu, linux-mm@kvack.org
Subject: Re: [PATCH] modified segq for 2.5
Date: Tue, 10 Sep 2002 03:50:43 +0200 [thread overview]
Message-ID: <E17oaAt-0006x4-00@starship> (raw)
In-Reply-To: <3D7D277E.7E179FA0@digeo.com>
On Tuesday 10 September 2002 00:58, Andrew Morton wrote:
> Daniel Phillips wrote:
> >
> > On Monday 09 September 2002 11:38, Andrew Morton wrote:
> > > One thing this patch did do was to speed up the initial untar of
> > > the kernel source - 50 seconds down to 25. That'll be due to not
> > > having so much dirt on the inactive list. The "nonblocking page
> > > reclaim" code (needs a better name...)
> >
> > Nonblocking kswapd, no? Perhaps 'kscand' would be a better name, now.
>
> Well, it blocks still. But it doesn't block on "this particular
> request queue" or on "that particular page ending IO". It
> blocks on "any queue putting back a write request". Which is
> basically equivalent to blocking on "a bunch of pages came clean".
It's not that far from being truly nonblocking, which would be a useful
property. Instead of calling ->writepage, just bump the page to the front of
the pdlist (getting deja vu here). Move locked pages off to a locked list
and let them rehabilitate themselves asynchronously (since we can now do lru
list moves inside interrupts). If necessary, fall back to scanning the
locked list for pages that slipped through the cracks, though it may be
possible to make things airtight so that never happens.
What other ways for kswapd to block are there? Buffers may be locked; a
similar strategy applies, which is one reason why buffer state should not be
opaque to the vfs. ->releasepage is a can of worms, at which I'm looking
suspiciously.
> Skipping is dumb. It shouldn't have been on that list in the
> first place.
Sure, it's not the only way to skin the cat. Anyway, skipping isn't so dumb
that we haven't been doing it for years.
--
Daniel
--
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-09-10 1:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 14:24 Rik van Riel
2002-09-09 9:38 ` Andrew Morton
2002-09-09 11:40 ` Ed Tomlinson
2002-09-09 17:10 ` William Lee Irwin III
2002-09-09 18:58 ` Andrew Morton
2002-09-09 13:10 ` Rik van Riel
2002-09-09 19:03 ` Andrew Morton
2002-09-09 19:25 ` Rik van Riel
2002-09-09 19:55 ` Andrew Morton
2002-09-09 20:03 ` Rik van Riel
2002-09-09 20:51 ` Andrew Morton
2002-09-09 20:57 ` Andrew Morton
2002-09-09 21:09 ` Rik van Riel
2002-09-09 21:52 ` Andrew Morton
2002-09-09 22:41 ` Rik van Riel
2002-09-10 0:17 ` Daniel Phillips
2002-09-09 22:49 ` William Lee Irwin III
2002-09-09 22:54 ` Rik van Riel
2002-09-09 23:32 ` William Lee Irwin III
2002-09-09 23:53 ` Rik van Riel
2002-09-09 22:46 ` Daniel Phillips
2002-09-09 22:58 ` Andrew Morton
2002-09-09 23:40 ` William Lee Irwin III
2002-09-10 0:02 ` Andrew Morton
2002-09-10 0:21 ` William Lee Irwin III
2002-09-10 1:13 ` Andrew Morton
2002-09-10 1:50 ` Daniel Phillips [this message]
2002-09-10 2:02 ` 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=E17oaAt-0006x4-00@starship \
--to=phillips@arcor.de \
--cc=akpm@digeo.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=sfkaplan@cs.amherst.edu \
--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