From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: tony.luck@intel.com
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
andi@firstfloor.org, fengguang.wu@intel.com,
liwanp@linux.vnet.ibm.com, david@fromorbit.com,
j-nomura@ce.jp.nec.com, linux-mm@kvack.org
Subject: Re: [PATCH 4/6] fs/proc/page.c: introduce /proc/kpagecache interface
Date: Thu, 13 Mar 2014 19:44:38 -0400 [thread overview]
Message-ID: <53224301.c19cc20a.23d5.7ed5SMTPIN_ADDED_BROKEN@mx.google.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31E04DD3@ORSMSX106.amr.corp.intel.com>
On Thu, Mar 13, 2014 at 11:09:10PM +0000, Luck, Tony wrote:
> > Usage is simple: 1) write a file path to be scanned into the interface,
> > and 2) read 64-bit entries, each of which is associated with the page on
> > each page index.
>
> Do we have other interfaces that work like that?
No, we don't. At first I thought of doing this under /proc/pid, but that did
not work because we want to scan the files which no process opens.
> I suppose this is file is only open
> to "root", so it may be safe to assume that applications using this won't stomp on
> each other.
Right, this is only for testing/debugging purpose (at least for now) so
limiting access is safe.
Thanks,
Naoya
--
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:[~2014-03-13 23:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 21:39 [PATCH 0/6] memory error report/recovery for dirty pagecache v3 Naoya Horiguchi
2014-03-13 21:39 ` [PATCH 1/6] radix-tree: add end_index to support ranged iteration Naoya Horiguchi
2014-03-13 21:39 ` [PATCH 2/6] mm/memory-failure.c: report and recovery for memory error on dirty pagecache Naoya Horiguchi
2014-03-15 3:17 ` Andi Kleen
2014-03-15 6:23 ` Naoya Horiguchi
2014-03-13 21:39 ` [PATCH 3/6] mm/memory-failure.c: add code to resolve quasi-hwpoisoned page Naoya Horiguchi
2014-03-13 21:39 ` [PATCH 4/6] fs/proc/page.c: introduce /proc/kpagecache interface Naoya Horiguchi
2014-03-13 23:09 ` Luck, Tony
2014-03-13 23:44 ` Naoya Horiguchi [this message]
2014-03-13 21:39 ` [PATCH 5/6] tools/vm/page-types.c: add file scanning mode Naoya Horiguchi
2014-03-13 21:39 ` [PATCH 6/6] Documentation: update Documentation/vm/pagemap.txt Naoya Horiguchi
2014-03-13 22:28 ` [PATCH 3/6] mm/memory-failure.c: add code to resolve quasi-hwpoisoned page Naoya Horiguchi
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=53224301.c19cc20a.23d5.7ed5SMTPIN_ADDED_BROKEN@mx.google.com \
--to=n-horiguchi@ah.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=tony.luck@intel.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