From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Martin Bligh <mbligh@google.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"nickpiggin@yahoo.com.au" <nickpiggin@yahoo.com.au>,
"Lee.Schermerhorn@hp.com" <Lee.Schermerhorn@hp.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] overwride page->mapping [0/3] intro
Date: Thu, 13 Sep 2007 10:27:05 +0900 [thread overview]
Message-ID: <20070913102705.91580d88.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709121804040.4912@schroedinger.engr.sgi.com>
On Wed, 12 Sep 2007 18:05:04 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:
> On Thu, 13 Sep 2007, KAMEZAWA Hiroyuki wrote:
>
> > Some machine may have very sparse address configuration from unknown(insane) reason.
>
> The HW engineers always find uses for those "unused" address bits.... And
> frankly we have done the same using a special address range for the VMEMMAP patchset.
>
I know (current) ia64 just uses 50bits.
Anyway, I think something like this
==
struct page_container * pfn_to_pagecontainer(unsigned long pfn);
#define page_to_container(page) pfn_to_pagecontainer(page_to_pfn(page))
==
is not very easy.
thanks,
-Kame
--
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>
prev parent reply other threads:[~2007-09-13 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 2:43 KAMEZAWA Hiroyuki
2007-09-12 2:45 ` [RFC][PATCH] overwride page->mapping [1/3] cleanup KAMEZAWA Hiroyuki
2007-09-12 2:47 ` [RFC][PATCH] overwride page->mapping [2/3] page_mapping_info KAMEZAWA Hiroyuki
2007-09-12 2:48 ` [RFC][PATCH] override page->mapping [3/3] mlock counter per page KAMEZAWA Hiroyuki
2007-09-12 8:42 ` [RFC][PATCH] overwride page->mapping [0/3] intro Balbir Singh
2007-09-12 13:28 ` KAMEZAWA Hiroyuki
2007-09-12 19:10 ` Christoph Lameter
2007-09-12 19:12 ` Martin Bligh
2007-09-12 19:17 ` Christoph Lameter
2007-09-13 0:32 ` KAMEZAWA Hiroyuki
2007-09-13 1:05 ` Christoph Lameter
2007-09-13 1:27 ` KAMEZAWA Hiroyuki [this message]
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=20070913102705.91580d88.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@google.com \
--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