From: Dave Hansen <haveblue@us.ibm.com>
To: akpm@linux-foundation.org
Cc: wfg@mail.ustc.edu.cn, balbir@linux.vnet.ibm.com,
jjberthels@gmail.com, mpm@selenic.com,
linux-mm <linux-mm@kvack.org>
Subject: Re: + maps2-export-page-index-in-kpagemap.patch added to -mm tree
Date: Mon, 24 Sep 2007 14:19:44 -0700 [thread overview]
Message-ID: <1190668784.26982.250.camel@localhost> (raw)
In-Reply-To: <200709242044.l8OKi01e016834@imap1.linux-foundation.org>
On Mon, 2007-09-24 at 13:44 -0700, akpm@linux-foundation.org wrote:
>
>
> To analyze/optimize the memory footprint, the number one question
> people
> may ask about pagemap/kpagemap could be:
>
> Which part of the files are being actively mapped?
>
> In the (rare) case of nonlinear mapping, that question could only be
> answered by explicitly exporting the page index in kpagemap. Simply
> judging by the PFNs from pagemap could be wrong!
I'll look over this in some more detail, but I have the feeling KPMSIZE
reintroduces the overrunning of users' buffers bug.
-- Dave
--
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:[~2007-09-24 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 20:44 + maps2-export-page-index-in-kpagemap.patch added to -mm tree akpm
2007-09-24 21:19 ` Dave Hansen [this message]
[not found] ` <20070924205901.GI19691@waste.org>
2007-09-24 21:23 ` Dave Hansen
2007-09-24 21:35 ` Matt Mackall
2007-09-24 21:50 ` Dave Hansen
2007-09-24 22:02 ` Matt Mackall
2007-09-25 7:19 ` Fengguang Wu
2007-09-25 7:19 ` Fengguang Wu
2007-09-25 8:17 ` Balbir Singh
2007-09-25 9:58 ` filecache: expose what's in the page cache Fengguang Wu
2007-09-25 9:58 ` Fengguang Wu
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=1190668784.26982.250.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=jjberthels@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=wfg@mail.ustc.edu.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.