linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Matt Mackall <mpm@selenic.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Andi Kleen <andi@firstfloor.org>,
	linux-mm@kvack.org
Subject: [PATCH 5/7] pagemap: document clarifications
Date: Thu, 07 May 2009 09:21:22 +0800	[thread overview]
Message-ID: <20090507014914.492422232@intel.com> (raw)
In-Reply-To: 20090507012116.996644836@intel.com

[-- Attachment #1: kpageflags-doc-fix.patch --]
[-- Type: text/plain, Size: 1402 bytes --]

Some bit ranges were inclusive and some not.
Fix them to be consistently inclusive.

Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
 Documentation/vm/pagemap.txt |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

--- linux.orig/Documentation/vm/pagemap.txt
+++ linux/Documentation/vm/pagemap.txt
@@ -12,9 +12,9 @@ There are three components to pagemap:
    value for each virtual page, containing the following data (from
    fs/proc/task_mmu.c, above pagemap_read):
 
-    * Bits 0-55  page frame number (PFN) if present
+    * Bits 0-54  page frame number (PFN) if present
     * Bits 0-4   swap type if swapped
-    * Bits 5-55  swap offset if swapped
+    * Bits 5-54  swap offset if swapped
     * Bits 55-60 page shift (page size = 1<<page shift)
     * Bit  61    reserved for future use
     * Bit  62    page swapped
@@ -36,7 +36,7 @@ There are three components to pagemap:
  * /proc/kpageflags.  This file contains a 64-bit set of flags for each
    page, indexed by PFN.
 
-   The flags are (from fs/proc/proc_misc, above kpageflags_read):
+   The flags are (from fs/proc/page.c, above kpageflags_read):
 
      0. LOCKED
      1. ERROR

-- 

--
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>

  parent reply	other threads:[~2009-05-07  1:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  1:21 [PATCH 0/7] export more page flags in /proc/kpageflags (take 5) Wu Fengguang
2009-05-07  1:21 ` [PATCH 1/7] mm: introduce PageHuge() for testing huge/gigantic pages Wu Fengguang
2009-05-07  1:21 ` [PATCH 2/7] slob: use PG_slab for identifying SLOB pages Wu Fengguang
2009-05-08 18:24   ` Matt Mackall
2009-05-07  1:21 ` [PATCH 3/7] proc: kpagecount/kpageflags code cleanup Wu Fengguang
2009-05-08 18:28   ` Matt Mackall
2009-05-07  1:21 ` [PATCH 4/7] proc: export more page flags in /proc/kpageflags Wu Fengguang
2009-05-07  2:04   ` Minchan Kim
2009-05-07  2:07     ` Wu Fengguang
2009-05-07  2:09       ` KOSAKI Motohiro
2009-05-07  2:20         ` Wu Fengguang
2009-05-07  2:40   ` Minchan Kim
2009-05-07  2:46     ` Wu Fengguang
2009-05-07  2:48       ` KOSAKI Motohiro
2009-05-07  3:05         ` Wu Fengguang
2009-05-07  1:21 ` Wu Fengguang [this message]
2009-05-07  1:21 ` [PATCH 6/7] pagemap: document 9 more exported page flags Wu Fengguang
2009-05-07  1:21 ` [PATCH 7/7] pagemap: add page-types tool Wu Fengguang

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=20090507014914.492422232@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.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;
as well as URLs for NNTP newsgroup(s).