All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Minchan Kim <minchan@kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
	KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Anton Vorontsov <anton.vorontsov@linaro.org>,
	Pekka Enberg <penberg@kernel.org>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Hugh Dickins <hughd@google.com>
Subject: Re: RFC:  Easy-Reclaimable LRU list
Date: Sat, 23 Jun 2012 13:45:28 +0900	[thread overview]
Message-ID: <4FE549E8.2050905@jp.fujitsu.com> (raw)
In-Reply-To: <4FE41752.8050305@kernel.org>

(2012/06/22 15:57), Minchan Kim wrote:
> Hi John,
>
> On 06/22/2012 04:21 AM, John Stultz wrote:
>
>> On 06/18/2012 10:49 PM, Minchan Kim wrote:
>>> Hi everybody!
>>>
>>> Recently, there are some efforts to handle system memory pressure.
>>>
>>> 1) low memory notification - [1]
>>> 2) fallocate(VOLATILE) - [2]
>>> 3) fadvise(NOREUSE) - [3]
>>>
>>> For them, I would like to add new LRU list, aka "Ereclaimable" which
>>> is opposite of "unevictable".
>>> Reclaimable LRU list includes _easy_ reclaimable pages.
>>> For example, easy reclaimable pages are following as.
>>>
>>> 1. invalidated but remained LRU list.
>>> 2. pageout pages for reclaim(PG_reclaim pages)
>>> 3. fadvise(NOREUSE)
>>> 4. fallocate(VOLATILE)
>>>
>>> Their pages shouldn't stir normal LRU list and compaction might not
>>> migrate them, even.
>>> Reclaimer can reclaim Ereclaimable pages before normal lru list and
>>> will avoid unnecessary
>>> swapout in anon pages in easy-reclaimable LRU list.
>>
>> I was hoping there would be further comment on this by more core VM
>> devs, but so far things have been quiet (is everyone on vacation?).
>
>
> At least, there are no dissent comment until now.
> Let be a positive. :)

I think this is interesting approach. Major concern is how to guarantee EReclaimable
pages are really EReclaimable...Do you have any idea ? madviced pages are really
EReclaimable ?

A (very) small concern is will you use one more page-flags for this ? ;)

Thanks,
-Kame






WARNING: multiple messages have this Message-ID (diff)
From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Minchan Kim <minchan@kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
	KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Anton Vorontsov <anton.vorontsov@linaro.org>,
	Pekka Enberg <penberg@kernel.org>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Hugh Dickins <hughd@google.com>
Subject: Re: RFC:  Easy-Reclaimable LRU list
Date: Sat, 23 Jun 2012 13:45:28 +0900	[thread overview]
Message-ID: <4FE549E8.2050905@jp.fujitsu.com> (raw)
In-Reply-To: <4FE41752.8050305@kernel.org>

(2012/06/22 15:57), Minchan Kim wrote:
> Hi John,
>
> On 06/22/2012 04:21 AM, John Stultz wrote:
>
>> On 06/18/2012 10:49 PM, Minchan Kim wrote:
>>> Hi everybody!
>>>
>>> Recently, there are some efforts to handle system memory pressure.
>>>
>>> 1) low memory notification - [1]
>>> 2) fallocate(VOLATILE) - [2]
>>> 3) fadvise(NOREUSE) - [3]
>>>
>>> For them, I would like to add new LRU list, aka "Ereclaimable" which
>>> is opposite of "unevictable".
>>> Reclaimable LRU list includes _easy_ reclaimable pages.
>>> For example, easy reclaimable pages are following as.
>>>
>>> 1. invalidated but remained LRU list.
>>> 2. pageout pages for reclaim(PG_reclaim pages)
>>> 3. fadvise(NOREUSE)
>>> 4. fallocate(VOLATILE)
>>>
>>> Their pages shouldn't stir normal LRU list and compaction might not
>>> migrate them, even.
>>> Reclaimer can reclaim Ereclaimable pages before normal lru list and
>>> will avoid unnecessary
>>> swapout in anon pages in easy-reclaimable LRU list.
>>
>> I was hoping there would be further comment on this by more core VM
>> devs, but so far things have been quiet (is everyone on vacation?).
>
>
> At least, there are no dissent comment until now.
> Let be a positive. :)

I think this is interesting approach. Major concern is how to guarantee EReclaimable
pages are really EReclaimable...Do you have any idea ? madviced pages are really
EReclaimable ?

A (very) small concern is will you use one more page-flags for this ? ;)

Thanks,
-Kame





--
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:[~2012-06-23  4:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  5:49 RFC: Easy-Reclaimable LRU list Minchan Kim
2012-06-19  5:49 ` Minchan Kim
2012-06-21 19:21 ` John Stultz
2012-06-21 19:21   ` John Stultz
2012-06-22  6:57   ` Minchan Kim
2012-06-22  6:57     ` Minchan Kim
2012-06-23  4:45     ` Kamezawa Hiroyuki [this message]
2012-06-23  4:45       ` Kamezawa Hiroyuki
2012-06-23 15:53       ` Rik van Riel
2012-06-23 15:53         ` Rik van Riel
2012-06-24 11:09         ` KOSAKI Motohiro
2012-06-24 11:09           ` KOSAKI Motohiro
2012-06-25  0:15       ` Minchan Kim
2012-06-25  0:15         ` Minchan Kim
2012-06-25  8:46 ` Glauber Costa
2012-06-25  8:46   ` Glauber Costa
2012-06-26  0:12   ` Minchan Kim
2012-06-26  0:12     ` Minchan Kim
2012-06-26  8:07     ` Glauber Costa
2012-06-26  8:07       ` Glauber Costa
2012-06-25 10:24 ` Mel Gorman
2012-06-25 10:24   ` Mel Gorman
2012-06-26  0:26   ` Minchan Kim
2012-06-26  0:26     ` Minchan Kim
2012-07-17 16:03   ` Zheng Liu
2012-07-17 16:03     ` Zheng Liu

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=4FE549E8.2050905@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton.vorontsov@linaro.org \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=john.stultz@linaro.org \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=penberg@kernel.org \
    --cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.