From: Alexey Lyahkov <alexey.lyashkov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>, Hugh Dickins <hughd@google.com>,
Bernd Schubert <bernd.schubert@fastmail.fm>,
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: Thu, 25 Apr 2013 11:18:17 +0300 [thread overview]
Message-ID: <8476E09F-D2DF-4685-A22F-0555475BD481@gmail.com> (raw)
In-Reply-To: <20130424144130.0d28b94b229b915d7f9c7840@linux-foundation.org>
So, right direction add ability to mark a page as active in lru pagevec array ?
just a bypass a IS_IN_LRU(page) check and fix moving to LRU to ability to put into active LRU list from pagevec ?
I may prepare a patch for it.
On Apr 25, 2013, at 00:41, Andrew Morton wrote:
> On Wed, 24 Apr 2013 10:26:50 -0400 "Theodore Ts'o" <tytso@mit.edu> wrote:
>
>> On Tue, Apr 23, 2013 at 03:00:08PM -0700, Andrew Morton wrote:
>>> That should fix things for now. Although it might be better to just do
>>>
>>> mark_page_accessed(page); /* to SetPageReferenced */
>>> lru_add_drain(); /* to SetPageLRU */
>>>
>>> Because a) this was too early to decide that the page is
>>> super-important and b) the second touch of this page should have a
>>> mark_page_accessed() in it already.
>>
>> The question is do we really want to put lru_add_drain() into the ext4
>> file system code? That seems to pushing some fairly mm-specific
>> knowledge into file system code. I'll do this if I have to do, but
>> wouldn't be better if this was pushed into mark_page_accessed(), or
>> some other new API was exported by the mm subsystem?
>
> Sure, that would be daft. We'd add a new
> mark_page_accessed_right_now_dont_use_this() to mm/swap.c
>
--
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-25 8:18 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 [this message]
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=8476E09F-D2DF-4685-A22F-0555475BD481@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=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