[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090705120659.GA5252@localhost>
Date: Sun, 5 Jul 2009 20:07:00 +0800
From: Wu Fengguang <fengguang.wu@...el.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc: LKML <linux-kernel@...r.kernel.org>, linux-mm <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>,
Rik van Riel <riel@...hat.com>
Subject: Re: [PATCH 2/5] add buffer cache information to show_free_areas()
On Sun, Jul 05, 2009 at 07:31:02PM +0800, KOSAKI Motohiro wrote:
> > On Sun, Jul 05, 2009 at 05:24:07PM +0800, KOSAKI Motohiro wrote:
> > > Subject: [PATCH] add buffer cache information to show_free_areas()
> > >
> > > When administrator analysis memory shortage reason from OOM log, They
> > > often need to know rest number of cache like pages.
> >
> > nr_blockdev_pages() pages are also accounted in NR_FILE_PAGES.
>
> Yes, I know.
>
> > > Then, show_free_areas() shouldn't only display page cache, but also it
> > > should display buffer cache.
> >
> > So if we are to add this, I'd suggest to put it close to the total
> > pagecache line:
> >
> > printk("%ld total pagecache pages\n", global_page_state(NR_FILE_PAGES));
> > + printk("%ld blkdev pagecache pages\n", nr_blockdev_pages());
>
> but this is intensional. May I explain why I choose non verbose area?
> In typical workload, buffer-pages doesn't consume so many pages. then
> I feel that your idea is too verbose output. In addition, if buffer-pages are much,
> Administrator want to know other I/O related vmstat at the same time.
> > > + " dirty:%lu writeback:%lu buffer:%lu unstable:%lu\n"
Now I see your point. It makes sense to put typically small numbers together.
Acked-by: Wu Fengguang <fengguang.wu@...el.com>
Thanks,
Fengguang
> > > Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
> > > ---
> > > mm/page_alloc.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > Index: b/mm/page_alloc.c
> > > ===================================================================
> > > --- a/mm/page_alloc.c
> > > +++ b/mm/page_alloc.c
> > > @@ -2118,7 +2118,7 @@ void show_free_areas(void)
> > > printk("Active_anon:%lu active_file:%lu inactive_anon:%lu\n"
> > > " inactive_file:%lu"
> > > " unevictable:%lu"
> > > - " dirty:%lu writeback:%lu unstable:%lu\n"
> > > + " dirty:%lu writeback:%lu buffer:%lu unstable:%lu\n"
> > > " free:%lu slab_reclaimable:%lu slab_unreclaimable:%lu\n"
> > > " mapped:%lu pagetables:%lu bounce:%lu\n",
> > > global_page_state(NR_ACTIVE_ANON),
> > > @@ -2128,6 +2128,7 @@ void show_free_areas(void)
> > > global_page_state(NR_UNEVICTABLE),
> > > global_page_state(NR_FILE_DIRTY),
> > > global_page_state(NR_WRITEBACK),
> > > + K(nr_blockdev_pages()),
> > > global_page_state(NR_UNSTABLE_NFS),
> > > global_page_state(NR_FREE_PAGES),
> > > global_page_state(NR_SLAB_RECLAIMABLE),
> > >
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists