From: Minchan Kim <minchan.kim@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andy Whitcroft <apw@canonical.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
riel@redhat.com
Subject: Re: [BUGFIX][PATCH] fix wrong lru rotate back at lumpty reclaim
Date: Tue, 9 Jun 2009 21:07:16 +0900 [thread overview]
Message-ID: <28c262360906090507u75f5b594o71906777a91efa1@mail.gmail.com> (raw)
In-Reply-To: <7ca0521d9b798ef8b56212e5b17ea713.squirrel@webmail-b.css.fujitsu.com>
2009/6/9 KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>:
> Minchan Kim wrote:
>
>> I mean follow as
>> 908 /*
>> 909 * Attempt to take all pages in the order aligned region
>> 910 * surrounding the tag page. Only take those pages of
>> 911 * the same active state as that tag page. We may safely
>> 912 * round the target page pfn down to the requested order
>> 913 * as the mem_map is guarenteed valid out to MAX_ORDER,
>> 914 * where that page is in a different zone we will detect
>> 915 * it from its zone id and abort this block scan.
>> 916 */
>> 917 zone_id = page_zone_id(page);
>>
> But what this code really do is.
> ==
> 931 /* Check that we have not crossed a zone
> boundary. */
> 932 if (unlikely(page_zone_id(cursor_page) !=
> zone_id))
> 933 continue;
> ==
> continue. I think this should be "break"
> I wonder what "This block scan" means is "scanning this aligned block".
It is to find first page in same zone with target page when we have
crossed a zone.
so it shouldn't stop due to that.
I think 'abort' means stopping only the page.
If it is right, it would be better to change follow as.
"and continue scanning next page"
Let's Cced Andy Whitcroft.
> But I think the whoe code is not written as commented.
>
>>
>>>> If I understand it properly , don't we add goto phrase ?
>>>>
>>> No.
>>
>> If it is so, the break also is meaningless.
>>
> yes. I'll remove it. But need to add "exit from for loop" logic again.
>
> I'm sorry that the wrong logic of this loop was out of my sight.
> I'll review and rewrite this part all, tomorrow.
Yes. I will review tomorrow, too. :)
> Thanks,
> -Kame
>
>
--
Kinds regards,
Minchan Kim
--
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-09 11:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 9:15 KAMEZAWA Hiroyuki
2009-06-09 9:22 ` [PATCH] memcg: fix mem_cgroup_isolate_lru_page to use the same rotate logic at busy path KAMEZAWA Hiroyuki
2009-06-09 12:04 ` Balbir Singh
2009-06-09 23:58 ` Daisuke Nishimura
2009-06-09 9:29 ` [BUGFIX][PATCH] fix wrong lru rotate back at lumpty reclaim KOSAKI Motohiro
2009-06-09 10:00 ` Minchan Kim
2009-06-09 11:20 ` KAMEZAWA Hiroyuki
2009-06-09 11:30 ` Minchan Kim
2009-06-09 11:47 ` KAMEZAWA Hiroyuki
2009-06-09 12:07 ` Minchan Kim [this message]
2009-06-09 13:00 ` Andy Whitcroft
2009-06-09 14:01 ` Minchan Kim
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=28c262360906090507u75f5b594o71906777a91efa1@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.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=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