linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Alexey Lyahkov <alexey.lyashkov@gmail.com>,
	Will Huck <will.huckk@gmail.com>, Hugh Dickins <hughd@google.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 14:02:37 +0200	[thread overview]
Message-ID: <5176785D.5030707@fastmail.fm> (raw)
In-Reply-To: <20130420235718.GA28789@thunk.org>

On 04/21/2013 01:57 AM, Theodore Ts'o wrote:
> On Sat, Apr 20, 2013 at 11:18:17PM +0200, Bernd Schubert wrote:
>> Alex, Andrew,
>>
>> did you notice the patch Ted just sent?
>> ("ext4: mark all metadata I/O with REQ_META")
>
> This patch was sent to fix another issue that was brought up at Linux
> Storage, Filesystem, and MM workshop.  I did bring up this issue with
> Mel Gorman while at LSF/MM, and as a result, tThe mm folks are going
> to look into making mark_page_accessed() do the right thing, or

Yeah, I know that REQ_META is a hint/flag for the IO scheduler.

> perhaps provide us with new interface.  The problem with forcing the
> page to be marked as activated is this would cause a TLB flush, which
> would be pointless since this these buddy bitmap pages aren't actually
> mapped in anywhere.

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.
I'm curious about outcome of the mm folks. Please let me know if there 
is anything I can help with.


Thanks,
Bernd





  parent reply	other threads:[~2013-04-23 12:02 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 [this message]
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
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=5176785D.5030707@fastmail.fm \
    --to=bernd.schubert@fastmail.fm \
    --cc=akpm@linux-foundation.org \
    --cc=alexey.lyashkov@gmail.com \
    --cc=anserper@ya.ru \
    --cc=hughd@google.com \
    --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).