[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090429000257.GB7601@sgi.com>
Date: Tue, 28 Apr 2009 19:02:57 -0500
From: Robin Holt <holt@....com>
To: Matt Mackall <mpm@...enic.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Tony Luck <tony.luck@...il.com>, fengguang.wu@...el.com,
mingo@...e.hu, rostedt@...dmis.org, fweisbec@...il.com,
lwoodman@...hat.com, a.p.zijlstra@...llo.nl,
penberg@...helsinki.fi, eduard.munteanu@...ux360.ro,
linux-kernel@...r.kernel.org, kosaki.motohiro@...fujitsu.com,
andi@...stfloor.org, adobriyan@...il.com, linux-mm@...ck.org
Subject: Re: [PATCH 5/5] proc: export more page flags in /proc/kpageflags
On Tue, Apr 28, 2009 at 04:49:55PM -0500, Matt Mackall wrote:
> > Reading the state of all of memory in this fashion would be a somewhat
> > peculiar thing to do.
>
> Not entirely. If you've got, say, a large NUMA box, it could be
> incredibly illustrative to see that "oh, this node is entirely dominated
> by SLAB allocations". Or on a smaller machine "oh, this is fragmented to
> hell and there's no way I'm going to get a huge page". Things you're not
> going to get from individual stats.
I have, in the past, simply used grep on
/sys/devices/system/node/node*/meminfo and gotten the individual stats
I was concerned about. Not sure how much more detail would have been
needed or useful. I don't think I can recall a time where I needed to
write another tool.
Thanks,
Robin
--
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