From: Minchan Kim <minchan.kim@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH 1/4] vmstat: remove zone->lock from walk_zones_in_node
Date: Tue, 29 Dec 2009 13:05:37 +0900 [thread overview]
Message-ID: <28c262360912282005x68315a62l7ffde637febc7646@mail.gmail.com> (raw)
In-Reply-To: <20091228164451.A687.A69D9226@jp.fujitsu.com>
On Mon, Dec 28, 2009 at 4:47 PM, KOSAKI Motohiro
<kosaki.motohiro@jp.fujitsu.com> wrote:
> The zone->lock is one of performance critical locks. Then, it shouldn't
> be hold for long time. Currently, we have four walk_zones_in_node()
> usage and almost use-case don't need to hold zone->lock.
I agree.
We can use walk_zone_in_node freely to show the information related to zone.
- frag_show_print : the number of free pages per order.
- pagetypeinfo_showfree_print : the number of free page per migration type
- pagetypeinfo_showblockcount_print : the number of pages in zone per
migration type
- zoneinfo_show_print : many info about zone.
Do we want to show exact value? No.
If we want it, it's not enough zone->lock only.
After all, All of things would be transient value.
>
> Thus, this patch move locking responsibility from walk_zones_in_node
> to its sub function. Also this patch kill unnecessary zone->lock taking.
>
> Cc: Mel Gorman <mel@csn.ul.ie>
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
--
Kind 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-12-29 4:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 7:47 KOSAKI Motohiro
2009-12-28 7:48 ` [PATCH 2/4] vmscan: get_scan_ratio cleanup KOSAKI Motohiro
2009-12-29 7:34 ` Balbir Singh
2009-12-30 13:06 ` KOSAKI Motohiro
2010-01-01 14:55 ` Rik van Riel
2010-01-03 23:45 ` KAMEZAWA Hiroyuki
2009-12-28 7:48 ` [PATCH 3/4] vmstat: add anon_scan_ratio field to zoneinfo KOSAKI Motohiro
2009-12-29 14:08 ` Balbir Singh
2009-12-30 13:13 ` KOSAKI Motohiro
2010-01-01 14:59 ` Rik van Riel
2010-01-03 23:47 ` KAMEZAWA Hiroyuki
2009-12-28 7:49 ` [PATCH 4/4] memcg: add anon_scan_ratio to memory.stat file KOSAKI Motohiro
2009-12-29 14:09 ` Balbir Singh
2009-12-30 12:53 ` KOSAKI Motohiro
2009-12-29 4:05 ` Minchan Kim [this message]
2009-12-29 6:34 ` [PATCH 1/4] vmstat: remove zone->lock from walk_zones_in_node Balbir Singh
2009-12-30 12:49 ` KOSAKI Motohiro
2010-01-03 18:59 ` Mel Gorman
2010-01-05 2:04 ` KOSAKI Motohiro
2010-01-05 10:18 ` Mel Gorman
2010-01-06 0:33 ` KOSAKI Motohiro
2010-01-03 23:48 ` 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=28c262360912282005x68315a62l7ffde637febc7646@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--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=mel@csn.ul.ie \
/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