Messages in this thread | | | Date | Thu, 28 Apr 2011 08:18:54 +0900 | Subject | Re: [RFC 3/8] vmscan: make isolate_lru_page with filter aware | From | Minchan Kim <> |
| |
On Wed, Apr 27, 2011 at 5:03 PM, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote: > On Wed, 27 Apr 2011 01:25:20 +0900 > Minchan Kim <minchan.kim@gmail.com> wrote: > >> In some __zone_reclaim case, we don't want to shrink mapped page. >> Nonetheless, we have isolated mapped page and re-add it into >> LRU's head. It's unnecessary CPU overhead and makes LRU churning. >> >> Of course, when we isolate the page, the page might be mapped but >> when we try to migrate the page, the page would be not mapped. >> So it could be migrated. But race is rare and although it happens, >> it's no big deal. >> >> Cc: Christoph Lameter <cl@linux.com> >> Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> >> Cc: Mel Gorman <mgorman@suse.de> >> Cc: Rik van Riel <riel@redhat.com> >> Cc: Andrea Arcangeli <aarcange@redhat.com> >> Signed-off-by: Minchan Kim <minchan.kim@gmail.com> > > > Hmm, it seems mm/memcontrol.c::mem_cgroup_isolate_pages() should be updated, too. > > But it's okay you start from global LRU.
Yes. That's exactly what I want. :) I am supposed to consider memcg after concept is approved.
> > Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Thanks fore the review, Kame. -- Kind regards, Minchan Kim
| |