From: Alexey Lyahkov <alexey.lyashkov@gmail.com>
To: Bernd Schubert <bernd.schubert@fastmail.fm>
Cc: Will Huck <will.huckk@gmail.com>, Hugh Dickins <hughd@google.com>,
Theodore Ts'o <tytso@mit.edu>, Andrew Perepechko <anserper@ya.ru>,
linux-ext4@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org
Subject: Re: page eviction from the buddy cache
Date: Mon, 22 Apr 2013 15:18:59 +0300 [thread overview]
Message-ID: <51874517-8D82-433E-9E10-13167C736D5F@gmail.com> (raw)
In-Reply-To: <51730619.3030204@fastmail.fm>
Bernd,
I fact marking REQ_META will help with io scheduler().
I and Andrew will discuss it's some time ago, but don't expect a too much performance improvements
anyway - i will pickup patch from Intel jira and ask performance engineer to evaluate it.
bw. My problem is in memory caching.
I may rewrite a buddy cache to avoid using a page cache at all as these pages but LRU aging will lost.
On Apr 21, 2013, at 00:18, Bernd Schubert wrote:
> Alex, Andrew,
>
> did you notice the patch Ted just sent?
> ("ext4: mark all metadata I/O with REQ_META")
>
> I would like to see a way to mark pages read in with REQ_META to be kept
> in cache preferred over other pages. I guess that would solve LU-15
> (https://jira.hpdd.intel.com/browse/LU-15) and also the direntry-block
> issue I tried to solve about 2 years ago
> (http://patchwork.ozlabs.org/patch/101200/). But using REQ_META to tag
> pages would probably also solve the same issue for other file systems.
> Is there anything already in the mm layer that could be used for that?
>
> Thanks,
> Bernd
>
--
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>
prev parent reply other threads:[~2013-04-22 12:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51504A40.6020604@ya.ru>
[not found] ` <20130327150743.GC14900@thunk.org>
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
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 [this message]
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=51874517-8D82-433E-9E10-13167C736D5F@gmail.com \
--to=alexey.lyashkov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anserper@ya.ru \
--cc=bernd.schubert@fastmail.fm \
--cc=hughd@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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