From: Dave Hansen <haveblue@us.ibm.com>
To: Matt Mackall <mpm@selenic.com>
Cc: akpm@linux-foundation.org, wfg@mail.ustc.edu.cn,
balbir@linux.vnet.ibm.com, jjberthels@gmail.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:23:08 -0700 [thread overview]
Message-ID: <1190668988.26982.254.camel@localhost> (raw)
In-Reply-To: <20070924205901.GI19691@waste.org>
On Mon, 2007-09-24 at 15:59 -0500, Matt Mackall wrote:
>
> If we really must do this, it'd be better to have a parallel file with
> the offsets.
Yeah, I'd much rather have a couple of files with really, really simple
and _stable_ formats than one with a more complex and variable one.
Although you can't answer the "which parts are mapped" question without
the page_index() information, you can answer the "what percentage of
this file is actively mapped" question.
Could someone elaborate a little bit more on exactly why you'd want to
know which parts of the file are mapped?
-- 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 20:15 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
[not found] ` <20070924205901.GI19691@waste.org>
2007-09-24 21:23 ` Dave Hansen [this message]
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=1190668988.26982.254.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.