From: Nikita Danilov <nikita@clusterfs.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH]: VM 8/8 shrink_list(): set PG_reclaimed
Date: Mon, 18 Apr 2005 20:18:48 +0400 [thread overview]
Message-ID: <16995.56808.736732.384860@gargle.gargle.HOWL> (raw)
In-Reply-To: <1113786837.5124.7.camel@npiggin-nld.site>
Nick Piggin writes:
> On Sun, 2005-04-17 at 21:38 +0400, Nikita Danilov wrote:
> > set PG_reclaimed bit on pages that are under writeback when shrink_list()
> > looks at them: these pages are at end of the inactive list, and it only makes
> > sense to reclaim them as soon as possible when writeout finishes.
> >
>
> I agree it makes sense, but this is racy I think. It will leave
> PG_reclaim set in some cases and hit bad_page. The trivial fix is
Good catch, thanks. By the way, bad_page() doesn't clear PG_reclaim that
free_pages_check() checks for. Is there some deep meaning in this?
> to remove the PG_reclaim check from bad_page. It looks a bit more
> tricky to do it "nicely".
>
I think "trivial fix" makes more sense, if we redefine PG_reclaim to
mean "page has been seen at end of the inactive list". This bit will be
set at the very beginning of shrink_list() (every for locked pages), and
cleared either by end-io handler, or when page is moved to the active
list. Idea being that if page made its way to end of the inactive list,
but VM failed to reclaim it due to some race, page should be reclaimed
as soon as possible (to get better LRU approximation).
Does this make sense?
>
> --
> SUSE Labs, Novell Inc.
Nikita.
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-04-18 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 17:38 Nikita Danilov
2005-04-18 1:13 ` Nick Piggin
2005-04-18 16:18 ` Nikita Danilov [this message]
2005-04-26 4:29 ` Andrew Morton
2005-04-26 5:27 ` Nick Piggin
2005-04-26 5:48 ` Nick Piggin
2005-04-26 10:16 ` Nikita Danilov
2005-04-26 10:29 ` Andrew Morton
2005-04-26 10:32 ` Nick Piggin
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=16995.56808.736732.384860@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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