From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
Bernd Schubert <bernd.schubert@fastmail.fm>,
Alexey Lyahkov <alexey.lyashkov@gmail.com>,
Will Huck <will.huckk@gmail.com>,
Andrew Perepechko <anserper@ya.ru>,
linux-ext4@vger.kernel.org, linux-mm@kvack.org, mgorman@suse.de
Subject: Re: page eviction from the buddy cache
Date: Tue, 23 Apr 2013 15:31:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.LNX.2.00.1304231518430.14137@eggly.anvils> (raw)
In-Reply-To: <20130423150008.046ee9351da4681128db0bf3@linux-foundation.org>
On Tue, 23 Apr 2013, Andrew Morton wrote:
> On Tue, 23 Apr 2013 12:57:45 -0700 (PDT) Hugh Dickins <hughd@google.com> wrote:
>
> I do agree that we should be able to set both PageReferenced and
> PageActive on a lru_add_pvecs page and have those hints honoured when
> lru_add_pvecs is spilled onto the LRU.
>
> At present the code decides up-front which LRU the lru_add_pvecs page
> will eventually be spilled onto. That's a bit strange and I wonder why
> we did it that way. Why not just have a single (per-cpu) magazine of
> pages which are to go onto the LRUs, and decide *which* LRU that will
> be at the last possible moment?
Yes, it is strange, and I'm wanting to get away from that: though I
won't be surprised if we discover that it's actually important for
avoiding races in the current scheme - which won't cope well with a
page being marked PageActive at the wrong moment (an instant after
it has been placed on the Inactive list).
What I want is for pages on the the per-cpu lru_add_pvecs to be already
marked PageLRU, and without raised page count, so that they are eligible
for isolation and migration without needing a drain. (But I may be too
ambitious in trying to avoid the raised page count for lru_rotate_pvecs
and the others too.)
Hugh
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-23 22:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 12:59 page eviction from the buddy cache Andrew Perepechko
2013-03-27 15:07 ` Theodore Ts'o
2013-03-27 19:24 ` Hugh Dickins
2013-03-28 5:34 ` Alexey Lyahkov
2013-04-04 1:24 ` Will Huck
2013-04-04 4:51 ` Alexey Lyahkov
2013-04-20 21:18 ` Bernd Schubert
2013-04-20 23:57 ` Theodore Ts'o
2013-04-22 12:14 ` Alexey Lyahkov
2013-04-23 12:02 ` Bernd Schubert
2013-04-23 12:27 ` Theodore Ts'o
2013-04-23 19:57 ` Hugh Dickins
2013-04-23 22:00 ` Andrew Morton
2013-04-23 22:31 ` Hugh Dickins [this message]
2013-04-24 14:26 ` Theodore Ts'o
2013-04-24 21:41 ` Andrew Morton
2013-04-25 8:18 ` Alexey Lyahkov
2013-04-25 14:30 ` Mel Gorman
2013-04-25 18:37 ` Alexey Lyahkov
2013-04-25 22:40 ` Mel Gorman
2013-04-26 6:03 ` Alexey Lyahkov
2013-04-22 12:18 ` Alexey Lyahkov
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=alpine.LNX.2.00.1304231518430.14137@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=alexey.lyashkov@gmail.com \
--cc=anserper@ya.ru \
--cc=bernd.schubert@fastmail.fm \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=tytso@mit.edu \
--cc=will.huckk@gmail.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;
as well as URLs for NNTP newsgroup(s).