From: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: Re: write drop behind effect on active scanning
Date: Wed, 23 May 2001 11:30:02 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10105231127480.11617-100000@coffee.psychology.mcmaster.ca> (raw)
In-Reply-To: <Pine.LNX.4.21.0105231022060.1874-100000@freak.distro.conectiva>
> > page->age = 0 ?
>
> That would make any full scan through the active list move all dropped
> pages from generic_file_write() to the inactive list.
well, that's where they're going, aren't they?
when these pages are unlocked, they should wind up on the
inactive-clean list. I think the real question is whether
it's worthwhile to make a separate locked list for them.
it certainly makes no sense to have them on a/ic/id while
they're locked, no?
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-23 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 7:33 Marcelo Tosatti
2001-05-23 14:33 ` Daniel Phillips
2001-05-23 13:25 ` Marcelo Tosatti
2001-05-23 15:30 ` Mark Hahn [this message]
2001-05-23 14:59 ` Marcelo Tosatti
2001-05-23 15:39 ` 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.10.10105231127480.11617-100000@coffee.psychology.mcmaster.ca \
--to=hahn@coffee.psychology.mcmaster.ca \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
/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