From: Rik van Riel <riel@redhat.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Minchan Kim <minchan@kernel.org>,
John Stultz <john.stultz@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>, 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 11:53:16 -0400 [thread overview]
Message-ID: <4FE5E66C.6080309@redhat.com> (raw)
In-Reply-To: <4FE549E8.2050905@jp.fujitsu.com>
On 06/23/2012 12:45 AM, Kamezawa Hiroyuki wrote:
> 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 ?
I suspect the EReclaimable pages can only be clean page
cache pages that are not mapped by any processes.
Once somebody tries to use the page, mark_page_accessed
will move it to another list.
> A (very) small concern is will you use one more page-flags for this ? ;)
This could be an issue on a 32 bit system, true.
--
All rights reversed
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Minchan Kim <minchan@kernel.org>,
John Stultz <john.stultz@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>, 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 11:53:16 -0400 [thread overview]
Message-ID: <4FE5E66C.6080309@redhat.com> (raw)
In-Reply-To: <4FE549E8.2050905@jp.fujitsu.com>
On 06/23/2012 12:45 AM, Kamezawa Hiroyuki wrote:
> 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 ?
I suspect the EReclaimable pages can only be clean page
cache pages that are not mapped by any processes.
Once somebody tries to use the page, mark_page_accessed
will move it to another list.
> A (very) small concern is will you use one more page-flags for this ? ;)
This could be an issue on a 32 bit system, true.
--
All rights reversed
--
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-23 15:53 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 [this message]
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=4FE5E66C.6080309@redhat.com \
--to=riel@redhat.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 \
/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.