From: Mel Gorman <mel@csn.ul.ie>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
apw@canonical.com, riel@redhat.com, minchan.kim@gmail.com
Subject: Re: [PATCH 1/3] remove wrong rotation at lumpy reclaim
Date: Thu, 11 Jun 2009 16:06:27 +0100 [thread overview]
Message-ID: <20090611150627.GH7302@csn.ul.ie> (raw)
In-Reply-To: <20090611170018.c3758488.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Jun 11, 2009 at 05:00:18PM +0900, KAMEZAWA Hiroyuki wrote:
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> At lumpy reclaim, a page failed to be taken by __isolate_lru_page() can
> be pushed back to "src" list by list_move(). But the page may not be from
> "src" list. And list_move() itself is unnecessary because the page is
> not on top of LRU. Then, leave it as it is if __isolate_lru_page() fails.
>
> This patch doesn't change the logic as "we should exit loop or not" and
> just fixes buggy list_move().
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> mm/vmscan.c | 9 +--------
> 1 file changed, 1 insertion(+), 8 deletions(-)
>
> Index: lumpy-reclaim-trial/mm/vmscan.c
> ===================================================================
> --- lumpy-reclaim-trial.orig/mm/vmscan.c
> +++ lumpy-reclaim-trial/mm/vmscan.c
> @@ -936,18 +936,11 @@ static unsigned long isolate_lru_pages(u
> /* Check that we have not crossed a zone boundary. */
> if (unlikely(page_zone_id(cursor_page) != zone_id))
> continue;
> - switch (__isolate_lru_page(cursor_page, mode, file)) {
> - case 0:
> + if (__isolate_lru_page(cursor_page, mode, file) == 0) {
> list_move(&cursor_page->lru, dst);
> nr_taken++;
> scan++;
> break;
> -
> - case -EBUSY:
> - /* else it is being freed elsewhere */
> - list_move(&cursor_page->lru, src);
> - default:
> - break; /* ! on LRU or wrong list */
> }
> }
> }
>
At very minimum, this avoids an unnecessary reshuffling of the LRU lists
during lumpy reclaim. Thanks
Acked-by: Mel Gorman <mel@csn.ul.ie>
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2009-06-11 15:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 7:55 [PATCH 0/3] misc fix around vmscan/isolate_lru_pages KAMEZAWA Hiroyuki
2009-06-11 8:00 ` [PATCH 1/3] remove wrong rotation at lumpy reclaim KAMEZAWA Hiroyuki
2009-06-11 8:21 ` KOSAKI Motohiro
2009-06-11 9:18 ` Minchan Kim
2009-06-11 11:13 ` KAMEZAWA Hiroyuki
2009-06-11 11:20 ` Minchan Kim
2009-06-11 22:52 ` Minchan Kim
2009-06-11 15:06 ` Mel Gorman [this message]
2009-06-11 8:01 ` [PATCH 2/3] check unevictable flag in lumy reclaim KAMEZAWA Hiroyuki
2009-06-11 8:24 ` KOSAKI Motohiro
2009-06-11 8:38 ` [PATCH 2/3] check unevictable flag in lumy reclaim v2 KAMEZAWA Hiroyuki
2009-06-11 8:44 ` KOSAKI Motohiro
2009-06-11 9:37 ` Minchan Kim
2009-06-11 9:39 ` Minchan Kim
2009-06-11 11:19 ` KAMEZAWA Hiroyuki
2009-06-11 11:59 ` Minchan Kim
2009-06-11 12:18 ` KAMEZAWA Hiroyuki
2009-06-11 22:55 ` Minchan Kim
2009-06-11 15:07 ` [PATCH 2/3] check unevictable flag in lumy reclaim Mel Gorman
2009-06-11 8:04 ` [PATCH 3/3] memcg: fix LRU rotation of isolate_lru_pages with memcg KAMEZAWA Hiroyuki
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=20090611150627.GH7302@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).