From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Christoph Lameter <cl@linux-foundation.org>,
Rik van Riel <riel@redhat.com>
Subject: [PATCH 2/4][resend] add buffer cache information to show_free_areas()
Date: Mon, 13 Jul 2009 15:01:12 +0900 (JST) [thread overview]
Message-ID: <20090713150021.625D.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090713144924.6257.A69D9226@jp.fujitsu.com>
ChangeLog
Since v3
- Rewrote the descriptin (Thanks Christoph!)
Since v2
- Changed display order, now, "buffer" field display right after unstable
Since v1
- Fixed showing the number with kilobyte unit issue
================
Subject: [PATCH] add buffer cache information to show_free_areas()
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.
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Acked-by: Wu Fengguang <fengguang.wu@intel.com>
Reviewed-by: Rik van Riel <riel@redhat.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 unstable:%lu buffer:%lu\n"
" free:%lu slab_reclaimable:%lu slab_unreclaimable:%lu\n"
" mapped:%lu pagetables:%lu bounce:%lu\n",
global_page_state(NR_ACTIVE_ANON),
@@ -2129,6 +2129,7 @@ void show_free_areas(void)
global_page_state(NR_FILE_DIRTY),
global_page_state(NR_WRITEBACK),
global_page_state(NR_UNSTABLE_NFS),
+ nr_blockdev_pages(),
global_page_state(NR_FREE_PAGES),
global_page_state(NR_SLAB_RECLAIMABLE),
global_page_state(NR_SLAB_UNRECLAIMABLE),
--
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-13 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 5:57 [PATCH 0/4] OOM analysis helper patch series v3 KOSAKI Motohiro
2009-07-13 6:00 ` [PATCH 1/4][resend] add per-zone statistics to show_free_areas() KOSAKI Motohiro
2009-07-13 6:01 ` KOSAKI Motohiro [this message]
2009-07-13 6:02 ` [PATCH 3/4][resend] Show kernel stack usage in /proc/meminfo and OOM log output KOSAKI Motohiro
2009-07-13 22:29 ` Andrew Morton
2009-07-13 23:36 ` KOSAKI Motohiro
2009-07-13 6:05 ` [PATCH 4/4][resend] add shmem vmstat KOSAKI Motohiro
2009-07-13 20:47 ` [PATCH 0/4] OOM analysis helper patch series v3 Rik van Riel
2009-07-13 23:38 ` KOSAKI Motohiro
2009-07-14 18:47 ` Li, Ming Chun
2009-07-14 23:38 ` 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=20090713150021.625D.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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