From: Glauber Costa <glommer@parallels.com>
To: Minchan Kim <minchan@kernel.org>
Cc: "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>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
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>,
John Stultz <john.stultz@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: Tue, 26 Jun 2012 12:07:11 +0400 [thread overview]
Message-ID: <4FE96DAF.3050208@parallels.com> (raw)
In-Reply-To: <4FE8FE70.6050107@kernel.org>
On 06/26/2012 04:12 AM, Minchan Kim wrote:
> On 06/25/2012 05:46 PM, Glauber Costa wrote:
>
>> On 06/19/2012 09:49 AM, 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.
>> What about other things moving memory like CMA ?
>
>
> Sorry for not being able to understand your point.
> Can you elaborate a bit more?
>
Well, maybe I didn't =)
I was just wondering why exactly it is that troubles your scheme with
compaction, and if such restriction would also apply to memory movement
schemes like CMA.
WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com>
To: Minchan Kim <minchan@kernel.org>
Cc: "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>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
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>,
John Stultz <john.stultz@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: Tue, 26 Jun 2012 12:07:11 +0400 [thread overview]
Message-ID: <4FE96DAF.3050208@parallels.com> (raw)
In-Reply-To: <4FE8FE70.6050107@kernel.org>
On 06/26/2012 04:12 AM, Minchan Kim wrote:
> On 06/25/2012 05:46 PM, Glauber Costa wrote:
>
>> On 06/19/2012 09:49 AM, 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.
>> What about other things moving memory like CMA ?
>
>
> Sorry for not being able to understand your point.
> Can you elaborate a bit more?
>
Well, maybe I didn't =)
I was just wondering why exactly it is that troubles your scheme with
compaction, and if such restriction would also apply to memory movement
schemes like CMA.
--
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:[~2012-06-26 8:10 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
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 [this message]
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=4FE96DAF.3050208@parallels.com \
--to=glommer@parallels.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=kamezawa.hiroyu@jp.fujitsu.com \
--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.