From: Christoph Lameter <cl@linux-foundation.org>
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>,
Wu Fengguang <fengguang.wu@intel.com>,
David Rientjes <rientjes@google.com>,
Rik van Riel <riel@redhat.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>
Subject: Re: [PATCH 2/5] add buffer cache information to show_free_areas()
Date: Thu, 9 Jul 2009 16:37:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0907091635070.17835@gentwo.org> (raw)
In-Reply-To: <20090709171027.23C0.A69D9226@jp.fujitsu.com>
On Thu, 9 Jul 2009, 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.
Maybe:
"
It is often useful to know the statistics for all pages that are handled
like page cache pages when looking at OOM log output.
Therefore show_free_areas() should also display buffer cache statistics.
"
--
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-09 20:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 8:05 [PATCH 0/5] OOM analysis helper patch series v2 KOSAKI Motohiro
2009-07-09 8:06 ` [PATCH 1/5][resend] add per-zone statistics to show_free_areas() KOSAKI Motohiro
2009-07-09 10:14 ` Minchan Kim
2009-07-09 14:59 ` Rik van Riel
2009-07-09 8:11 ` [PATCH 2/5] add buffer cache information " KOSAKI Motohiro
2009-07-09 15:00 ` Rik van Riel
2009-07-09 20:37 ` Christoph Lameter [this message]
2009-07-09 23:39 ` KOSAKI Motohiro
2009-07-09 8:12 ` [PATCH 3/5][resend] Show kernel stack usage to /proc/meminfo and OOM log KOSAKI Motohiro
2009-07-09 10:20 ` Minchan Kim
2009-07-09 15:01 ` Rik van Riel
2009-07-09 20:38 ` Christoph Lameter
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
2009-07-09 8:18 ` [PATCH 5/5] add shmem vmstat KOSAKI Motohiro
2009-07-09 15:03 ` Rik van Riel
2009-07-09 20:46 ` Christoph Lameter
2009-07-10 1:23 ` Wu Fengguang
2009-07-09 10:41 ` [PATCH 0/5] OOM analysis helper patch series v2 Minchan Kim
2009-07-09 17:51 ` Li, Ming Chun
2009-07-09 22:05 ` Li, Ming Chun
2009-07-09 23:35 ` KOSAKI Motohiro
2009-07-10 2:17 ` KOSAKI Motohiro
2009-07-10 16:54 ` Li, Ming Chun
-- strict thread matches above, loose matches on Subject: below --
2009-07-05 9:22 [PATCH 0/5] OOM analysis helper patches KOSAKI Motohiro
2009-07-05 9:24 ` [PATCH 2/5] add buffer cache information to show_free_areas() 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
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=alpine.DEB.1.10.0907091635070.17835@gentwo.org \
--to=cl@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hugh.dickins@tiscali.co.uk \
--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