From: Minchan Kim <minchan.kim@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 4/5] add isolate pages vmstat
Date: Sun, 5 Jul 2009 23:51:46 +0900 [thread overview]
Message-ID: <28c262360907050751t1fccbf4t4ace572b4e003a13@mail.gmail.com> (raw)
In-Reply-To: <20090705211127.0917.A69D9226@jp.fujitsu.com>
On Sun, Jul 5, 2009 at 9:23 PM, KOSAKI
Motohiro<kosaki.motohiro@jp.fujitsu.com> wrote:
>> On Sun, Jul 05, 2009 at 05:25:32PM +0800, KOSAKI Motohiro wrote:
>> > Subject: [PATCH] add isolate pages vmstat
>> >
>> > If the system have plenty threads or processes, concurrent reclaim can
>> > isolate very much pages.
>> > Unfortunately, current /proc/meminfo and OOM log can't show it.
>> >
>> > This patch provide the way of showing this information.
>> >
>> >
>> > reproduce way
>> > -----------------------
>> > % ./hackbench 140 process 1000
>> > => couse OOM
>> >
>> > Active_anon:4419 active_file:120 inactive_anon:1418
>> > inactive_file:61 unevictable:0 isolated:45311
>> > ^^^^^
>> > dirty:0 writeback:580 unstable:0
>> > free:27 slab_reclaimable:297 slab_unreclaimable:4050
>> > mapped:221 kernel_stack:5758 pagetables:28219 bounce:0
>> >
>> >
>> >
>> > Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>> > ---
>> > drivers/base/node.c | 2 ++
>> > fs/proc/meminfo.c | 2 ++
>> > include/linux/mmzone.h | 1 +
>> > mm/page_alloc.c | 6 ++++--
>> > mm/vmscan.c | 4 ++++
>> > mm/vmstat.c | 2 +-
>> > 6 files changed, 14 insertions(+), 3 deletions(-)
>> >
>> > Index: b/fs/proc/meminfo.c
>> > ===================================================================
>> > --- a/fs/proc/meminfo.c
>> > +++ b/fs/proc/meminfo.c
>> > @@ -65,6 +65,7 @@ static int meminfo_proc_show(struct seq_
>> > "Active(file): %8lu kB\n"
>> > "Inactive(file): %8lu kB\n"
>> > "Unevictable: %8lu kB\n"
>> > + "IsolatedPages: %8lu kB\n"
>> > "Mlocked: %8lu kB\n"
>> > #ifdef CONFIG_HIGHMEM
>> > "HighTotal: %8lu kB\n"
>> > @@ -109,6 +110,7 @@ static int meminfo_proc_show(struct seq_
>> > K(pages[LRU_ACTIVE_FILE]),
>> > K(pages[LRU_INACTIVE_FILE]),
>> > K(pages[LRU_UNEVICTABLE]),
>> > + K(global_page_state(NR_ISOLATED)),
>>
>> Glad to see you renamed it to NR_ISOLATED :)
>> But for the user visible name, how about IsolatedLRU?
>
> Ah, nice. below is update patch.
>
> Changelog
> ----------------
> since v1
> - rename "IsolatedPages" to "IsolatedLRU"
>
>
> =================================
> Subject: [PATCH] add isolate pages vmstat
>
> If the system have plenty threads or processes, concurrent reclaim can
> isolate very much pages.
> Unfortunately, current /proc/meminfo and OOM log can't show it.
>
> This patch provide the way of showing this information.
>
>
> reproduce way
> -----------------------
> % ./hackbench 140 process 1000
> => couse OOM
>
> Active_anon:4419 active_file:120 inactive_anon:1418
> inactive_file:61 unevictable:0 isolated:45311
> ^^^^^
> dirty:0 writeback:580 unstable:0
> free:27 slab_reclaimable:297 slab_unreclaimable:4050
> mapped:221 kernel_stack:5758 pagetables:28219 bounce:0
>
>
>
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> Acked-by: Wu Fengguang <fengguang.wu@intel.com>
> ---
> drivers/base/node.c | 2 ++
> fs/proc/meminfo.c | 2 ++
> include/linux/mmzone.h | 1 +
> mm/page_alloc.c | 6 ++++--
> mm/vmscan.c | 4 ++++
> mm/vmstat.c | 2 +-
> 6 files changed, 14 insertions(+), 3 deletions(-)
>
> Index: b/fs/proc/meminfo.c
> ===================================================================
> --- a/fs/proc/meminfo.c
> +++ b/fs/proc/meminfo.c
> @@ -65,6 +65,7 @@ static int meminfo_proc_show(struct seq_
> "Active(file): %8lu kB\n"
> "Inactive(file): %8lu kB\n"
> "Unevictable: %8lu kB\n"
> + "IsolatedLRU: %8lu kB\n"
> "Mlocked: %8lu kB\n"
> #ifdef CONFIG_HIGHMEM
> "HighTotal: %8lu kB\n"
> @@ -109,6 +110,7 @@ static int meminfo_proc_show(struct seq_
> K(pages[LRU_ACTIVE_FILE]),
> K(pages[LRU_INACTIVE_FILE]),
> K(pages[LRU_UNEVICTABLE]),
> + K(global_page_state(NR_ISOLATED)),
> K(global_page_state(NR_MLOCK)),
> #ifdef CONFIG_HIGHMEM
> K(i.totalhigh),
> Index: b/include/linux/mmzone.h
> ===================================================================
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -100,6 +100,7 @@ enum zone_stat_item {
> NR_BOUNCE,
> NR_VMSCAN_WRITE,
> NR_WRITEBACK_TEMP, /* Writeback using temporary buffers */
> + NR_ISOLATED, /* Temporary isolated pages from lru */
> #ifdef CONFIG_NUMA
> NUMA_HIT, /* allocated in intended node */
> NUMA_MISS, /* allocated in non intended node */
> Index: b/mm/page_alloc.c
> ===================================================================
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -2116,8 +2116,7 @@ void show_free_areas(void)
> }
>
> printk("Active_anon:%lu active_file:%lu inactive_anon:%lu\n"
> - " inactive_file:%lu"
> - " unevictable:%lu"
> + " inactive_file:%lu unevictable:%lu isolated:%lu\n"
It's good.
I have a one suggestion.
I know this patch came from David's OOM problem a few days ago.
I think total pages isolated of all lru doesn't help us much.
It just represents why [in]active[anon/file] is zero.
How about adding isolate page number per each lru ?
IsolatedPages(file)
IsolatedPages(anon)
It can help knowing exact number of each lru.
--
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-07-05 17:08 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 9:22 [PATCH 0/5] OOM analysis helper patches KOSAKI Motohiro
2009-07-05 9:23 ` [PATCH 1/5] add per-zone statistics to show_free_areas() KOSAKI Motohiro
2009-07-05 11:05 ` Wu Fengguang
2009-07-05 11:09 ` KOSAKI Motohiro
2009-07-05 11:14 ` Wu Fengguang
2009-07-07 16:33 ` Christoph Lameter
2009-07-05 9:24 ` [PATCH 2/5] add buffer cache information " KOSAKI Motohiro
2009-07-05 11:21 ` Wu Fengguang
2009-07-05 11:31 ` KOSAKI Motohiro
2009-07-05 12:07 ` Wu Fengguang
2009-07-05 14:16 ` Minchan Kim
2009-07-06 4:24 ` KOSAKI Motohiro
2009-07-05 9:24 ` [PATCH 3/5] Show kernel stack usage to /proc/meminfo and OOM log KOSAKI Motohiro
2009-07-07 16:37 ` Christoph Lameter
2009-07-09 2:13 ` KOSAKI Motohiro
2009-07-09 21:00 ` Christoph Lameter
2009-07-05 9:25 ` [PATCH 4/5] add isolate pages vmstat KOSAKI Motohiro
2009-07-05 12:10 ` Wu Fengguang
2009-07-05 12:23 ` KOSAKI Motohiro
2009-07-05 14:51 ` Minchan Kim [this message]
2009-07-06 9:28 ` KOSAKI Motohiro
2009-07-06 11:55 ` KOSAKI Motohiro
2009-07-07 0:01 ` Minchan Kim
2009-07-07 0:07 ` KOSAKI Motohiro
2009-07-07 1:19 ` KOSAKI Motohiro
2009-07-07 1:48 ` Minchan Kim
2009-07-07 2:12 ` KOSAKI Motohiro
2009-07-07 2:31 ` Minchan Kim
2009-07-07 3:02 ` Rik van Riel
2009-07-07 13:51 ` Wu Fengguang
2009-07-07 16:49 ` Christoph Lameter
2009-07-07 17:23 ` Rik van Riel
2009-07-07 23:32 ` Christoph Lameter
2009-07-09 2:19 ` KOSAKI Motohiro
2009-07-09 21:00 ` Christoph Lameter
2009-07-07 16:46 ` Christoph Lameter
2009-07-08 1:44 ` Wu Fengguang
2009-07-05 9:26 ` [PATCH 5/5] add NR_ANON_PAGES to OOM log KOSAKI Motohiro
2009-07-05 12:13 ` Wu Fengguang
2009-07-05 12:21 ` KOSAKI Motohiro
2009-07-05 13:02 ` Wu Fengguang
2009-07-05 13:19 ` KOSAKI Motohiro
2009-07-05 15:04 ` Minchan Kim
2009-07-05 15:16 ` Wu Fengguang
2009-07-05 15:27 ` Minchan Kim
2009-07-07 16:53 ` Christoph Lameter
2009-07-09 5:50 ` KOSAKI Motohiro
2009-07-09 7:20 ` KOSAKI Motohiro
2009-07-09 10:27 ` Minchan Kim
2009-07-07 1:22 ` KOSAKI Motohiro
2009-07-07 10:54 ` Wu Fengguang
2009-07-07 13:56 ` Wu Fengguang
2009-07-09 5:13 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2009-07-09 8:05 [PATCH 0/5] OOM analysis helper patch series v2 KOSAKI Motohiro
2009-07-09 8:14 ` [PATCH 4/5] add isolate pages vmstat KOSAKI Motohiro
2009-07-09 10:22 ` Minchan Kim
2009-07-09 20:43 ` Christoph Lameter
2009-07-10 2:11 ` KOSAKI Motohiro
2009-07-10 18:48 ` Christoph Lameter
2009-07-13 1:50 ` KOSAKI Motohiro
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=28c262360907050751t1fccbf4t4ace572b4e003a13@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=rientjes@google.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).