From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Christoph Lameter <cl@linux-foundation.org>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Chris Wright <chrisw@redhat.com>, Izik Eidus <ieidus@redhat.com>
Subject: [PATCH] pagemap: document KPF_KSM and show it in page-types
Date: Mon, 31 Aug 2009 15:17:02 +0800 [thread overview]
Message-ID: <20090831071702.GB26634@localhost> (raw)
In-Reply-To: <20090831071425.GA26634@localhost>
It indicates to the system admin that processes mapping such pages may be
eating less physical memory than the reported numbers by legacy tools.
CC: Hugh Dickins <hugh.dickins@tiscali.co.uk>
CC: Chris Wright <chrisw@redhat.com>
CC: Izik Eidus <ieidus@redhat.com>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
Documentation/vm/pagemap.txt | 4 ++++
tools/vm/page-types.c | 2 ++
2 files changed, 6 insertions(+)
--- linux-mm.orig/Documentation/vm/pagemap.txt 2009-08-31 15:02:55.000000000 +0800
+++ linux-mm/Documentation/vm/pagemap.txt 2009-08-31 15:05:02.000000000 +0800
@@ -59,6 +59,7 @@ There are three components to pagemap:
18. UNEVICTABLE
19. HWPOISON
20. NOPAGE
+ 21. KSM
Short descriptions to the page flags:
@@ -93,6 +94,9 @@ Short descriptions to the page flags:
20. NOPAGE
no page frame exists at the requested address
+21. KSM
+ identical memory pages dynamicly shared between one or more processes
+
[IO related page flags]
1. ERROR IO error occurred
3. UPTODATE page has up-to-date data
--- linux-mm.orig/tools/vm/page-types.c 2009-08-31 15:00:24.000000000 +0800
+++ linux-mm/tools/vm/page-types.c 2009-08-31 15:02:10.000000000 +0800
@@ -49,6 +49,7 @@
#define KPF_UNEVICTABLE 18
#define KPF_HWPOISON 19
#define KPF_NOPAGE 20
+#define KPF_KSM 21
/* [32-] kernel hacking assistances */
#define KPF_RESERVED 32
@@ -97,6 +98,7 @@ static char *page_flag_names[] = {
[KPF_UNEVICTABLE] = "u:unevictable",
[KPF_HWPOISON] = "X:hwpoison",
[KPF_NOPAGE] = "n:nopage",
+ [KPF_KSM] = "x:ksm",
[KPF_RESERVED] = "r:reserved",
[KPF_MLOCKED] = "m:mlocked",
next prev parent reply other threads:[~2009-08-31 7:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 17:39 [PATCH] Documentation/vm/.gitignore: Add page-types Josh Triplett
2009-08-12 6:51 ` Wu Fengguang
2009-08-31 4:58 ` KOSAKI Motohiro
2009-08-31 6:56 ` [PATCH] page-types: move from Documentation/vm/ to tools/vm/ Wu Fengguang
2009-08-31 7:14 ` [PATCH] pagemap: export KPF_HWPOISON Wu Fengguang
2009-08-31 7:17 ` Wu Fengguang [this message]
2009-08-31 15:39 ` [PATCH] pagemap: document KPF_KSM and show it in page-types Randy Dunlap
2009-09-01 7:55 ` Wu Fengguang
2009-09-01 8:00 ` [PATCH -v2] " Wu Fengguang
2009-08-31 16:41 ` [PATCH] " Chris Wright
2009-09-01 7:58 ` Wu Fengguang
2009-08-31 7:18 ` [PATCH] pagemap: export KPF_HWPOISON KOSAKI Motohiro
2009-09-01 17:50 ` [PATCH] page-types: move from Documentation/vm/ to tools/vm/ Christoph Lameter
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=20090831071702.GB26634@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=chrisw@redhat.com \
--cc=cl@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=ieidus@redhat.com \
--cc=josh@joshtriplett.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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).