linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: 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, akpm@linux-foundation.org,
	linux-mm@kvack.org, mgorman@suse.de
Subject: Re: page eviction from the buddy cache
Date: Tue, 23 Apr 2013 12:57:45 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1304231230340.12850@eggly.anvils> (raw)
In-Reply-To: <20130423122708.GA31170@thunk.org>

On Tue, 23 Apr 2013, Theodore Ts'o wrote:
> On Tue, Apr 23, 2013 at 02:02:37PM +0200, Bernd Schubert wrote:
> > 
> > I just thought we can (mis)use that flag and and add another
> > information to the page that it holds meta data. The mm system then
> > could use that flag and evict those pages with a lower priority
> > compared to other pages.
> 
> Well, the flag I added was to the buffer_head, not to the page, and my
> understanding is that the mm folks are very hesitant to add new page
> flags, since they are bumping up against the 32 bit limit (on the i386
> platform), and they are trying to keep the struct page structure trim
> and svelte.  :-)

Yes indeed.  But luckily this issue seems not to need another page flag.

If metadata is useful, it gets used: so mark_page_accessed when it's used
should generally do the job; perhaps it's already called on that path,
perhaps calls need to be added.

Rarely used but nonetheless useful metadata might get pushed out by data.
But I don't think we want another page flag, and yet more complicated
reclaim policy in mm for that case.  If the filesystem knows of such
cases, I hope it can find a way to use mark_page_accessed more often
on such pages than they are actually accessed, to help retain them.

What this thread did bring up was the failure of mark_page_accessed
to be fully effective until the page is flushed from pagevec to lru.
That remains a good point: something that several would like to fix.

For now I stand by what I said before (if you find it effective
in practice - I haven't heard back): at the moment you need to

	mark_page_accessed(page);	/* to SetPageReferenced */
	lru_add_drain();		/* to SetPageLRU */
	mark_page_accessed(page);	/* to SetPageActive */

when such a metadata page is first brought in.

We all hate that lru_add_drain in the middle, which will exacerbate
lru_lock contention.  We would love to eliminate the need for most
lru_add_drains: I have some ideas which I'm pursuing in odd moments,
but I promise nothing.

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>

  reply	other threads:[~2013-04-23 19:57 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 [this message]
2013-04-23 22:00                     ` Andrew Morton
2013-04-23 22:31                       ` Hugh Dickins
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.1304231230340.12850@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).