From: Rik van Riel <riel@conectiva.com.br>
To: Andrew Morton <akpm@zip.com.au>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: nonblocking-vm.patch
Date: Wed, 4 Sep 2002 19:12:02 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44L.0209041909430.1857-100000@imladris.surriel.com> (raw)
In-Reply-To: <3D767F45.97D8AAC9@zip.com.au>
On Wed, 4 Sep 2002, Andrew Morton wrote:
> OK. We need to start getting some of that stuff going now. We're
> way too swappy at present. I'll merge up your NRU/dropbehind
> patch soon. I imagine that you're waiting for me to stop changing
> things.
You seemed busy enough already ;)
> > 3) if the page is written to disk, keep it at the end of
> > the list where we start scanning from
>
> hum. With the clustered-writeback-from-the-vm regime, this is
> done over in mpage_writepages(). And that walks mapping->dirty_pages,
> and moves the pages to the hot end of the inactive list (if they're
> already on the inactive list).
>
> I suppose we could just move them to the cold end and scan past them,
> but that's a bit lazy.
Better yet, just leave them in place and scan over them only if
they aren't cleaned yet when they reach the end of the list.
The closer page reclaim is done to pure LRU order, the smoother
the VM seems to work. Quite possibly this is a side effect of
not doing too much IO at once, but still ... ;)
> > 4) if we don't write the page to disk (I don't submit too
> > much IO at once) we move it to the far end of the inactive
> > list
> >
> > This means that the pages for which IO completed will be found
> > somewhere near the start of the list.
>
> OK.
>
> (Why don't you move them over to inactive_dirty? I've never understood
> those two lists. I suspect the names are misleading?)
Sorry, I should have been clearer here.
Page_launder (shrink_cache) scans the inactive_dirty list.
Pages which are ready to be reclaimed get moved to the inactive_clean
list, from where __alloc_pages() deals with them.
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-09-04 22:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 10:28 nonblocking-vm.patch Andrew Morton
2002-09-04 13:32 ` nonblocking-vm.patch Rik van Riel
2002-09-04 18:44 ` nonblocking-vm.patch Andrew Morton
2002-09-04 19:42 ` nonblocking-vm.patch Rik van Riel
2002-09-04 20:14 ` nonblocking-vm.patch Andrew Morton
2002-09-04 20:55 ` nonblocking-vm.patch Rik van Riel
2002-09-04 21:22 ` nonblocking-vm.patch Andrew Morton
2002-09-04 21:34 ` nonblocking-vm.patch Rik van Riel
2002-09-04 21:46 ` nonblocking-vm.patch Andrew Morton
2002-09-04 22:12 ` Rik van Riel [this message]
2002-09-04 22:41 ` nonblocking-vm.patch Andrew Morton
2002-09-04 22:46 ` nonblocking-vm.patch Rik van Riel
2002-09-05 5:43 ` nonblocking-vm.patch Andrew Morton
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.0209041909430.1857-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=akpm@zip.com.au \
--cc=linux-mm@kvack.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