From: Dave Hansen <haveblue@us.ibm.com>
To: Yasunori Goto <ygoto@us.fujitsu.com>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>,
Linux-Node-Hotplug <lhns-devel@lists.sourceforge.net>,
linux-mm <linux-mm@kvack.org>,
"BRADLEY CHRISTIANSEN [imap]" <bradc1@us.ibm.com>
Subject: Re: [Lhms-devel] Re: Merging Nonlinear and Numa style memory hotplug
Date: Thu, 24 Jun 2004 20:19:01 -0700 [thread overview]
Message-ID: <1088133541.3918.1348.camel@nighthawk> (raw)
In-Reply-To: <20040624194557.F02B.YGOTO@us.fujitsu.com>
On Thu, 2004-06-24 at 20:11, Yasunori Goto wrote:
> I understand this idea at last.
> Section size of DLPAR of PPC is only 16MB.
> But kmalloc area of virtual address have to be contigous
> even if the area is divided 16MB physically.
> Dave-san's implementation (it was for IA32) was same index between
> phys_section and mem_section. So, I was confused.
>
> > pfn_to_page(unsigned long pfn)
> > {
> > return
> > &mem_section[phys_section[pfn_to_section(pfn)]].mem_map[section_offset_pfn(pfn)];
> > }
> >
>
> But, I suppose this translation might be too complex.
It certainly doesn't look pretty, but I think it's manageable with a
comment, or maybe breaking the operation up into a few lines instead.
> I worry that many person don't like this which is cause of
> performance deterioration.
There is some precedent in the kernel for a table such as this. Take a
look at the NUMA page_to_pfn() and page_zone() functions. They use a
zone_table array to do that same kind of thing.
Are you worried bout the pfn_to_page() function itself, that it will
pull in 2 cachelines of data: 1 for phys_section[] and another for
mem_section[]?
> Should this translation be in common code?
What do you mean by common code? It should be shared by all
architectures.
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Yasunori Goto <ygoto@us.fujitsu.com>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>,
Linux-Node-Hotplug <lhns-devel@lists.sourceforge.net>,
linux-mm <linux-mm@kvack.org>,
"BRADLEY CHRISTIANSEN [imap]" <bradc1@us.ibm.com>
Subject: Re: [Lhms-devel] Re: Merging Nonlinear and Numa style memory hotplug
Date: Thu, 24 Jun 2004 20:19:01 -0700 [thread overview]
Message-ID: <1088133541.3918.1348.camel@nighthawk> (raw)
In-Reply-To: <20040624194557.F02B.YGOTO@us.fujitsu.com>
On Thu, 2004-06-24 at 20:11, Yasunori Goto wrote:
> I understand this idea at last.
> Section size of DLPAR of PPC is only 16MB.
> But kmalloc area of virtual address have to be contigous
> even if the area is divided 16MB physically.
> Dave-san's implementation (it was for IA32) was same index between
> phys_section and mem_section. So, I was confused.
>
> > pfn_to_page(unsigned long pfn)
> > {
> > return
> > &mem_section[phys_section[pfn_to_section(pfn)]].mem_map[section_offset_pfn(pfn)];
> > }
> >
>
> But, I suppose this translation might be too complex.
It certainly doesn't look pretty, but I think it's manageable with a
comment, or maybe breaking the operation up into a few lines instead.
> I worry that many person don't like this which is cause of
> performance deterioration.
There is some precedent in the kernel for a table such as this. Take a
look at the NUMA page_to_pfn() and page_zone() functions. They use a
zone_table array to do that same kind of thing.
Are you worried bout the pfn_to_page() function itself, that it will
pull in 2 cachelines of data: 1 for phys_section[] and another for
mem_section[]?
> Should this translation be in common code?
What do you mean by common code? It should be shared by all
architectures.
-- 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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-06-25 3:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 19:00 Merging Nonlinear and Numa style memory hotplug Yasunori Goto
2004-06-22 19:00 ` Yasunori Goto
2004-06-23 22:32 ` [Lhns-devel] " Dave Hansen
2004-06-23 22:32 ` Dave Hansen
2004-06-24 3:04 ` Yasunori Goto
2004-06-24 3:04 ` Yasunori Goto
2004-06-24 3:26 ` Dave Hansen
2004-06-24 3:26 ` Dave Hansen
2004-06-24 13:28 ` [Lhms-devel] " Dave Hansen
2004-06-24 13:28 ` Dave Hansen
2004-06-24 22:19 ` Yasunori Goto
2004-06-24 22:19 ` Yasunori Goto
2004-06-24 22:37 ` Dave Hansen
2004-06-24 22:37 ` Dave Hansen
2004-06-25 3:11 ` [Lhms-devel] " Yasunori Goto
2004-06-25 3:11 ` Yasunori Goto
2004-06-25 3:19 ` Dave Hansen [this message]
2004-06-25 3:19 ` Dave Hansen
2004-06-25 18:48 ` Yasunori Goto
2004-06-25 18:48 ` Yasunori Goto
2004-06-25 18:59 ` Dave Hansen
2004-06-25 18:59 ` Dave Hansen
2004-06-25 20:45 ` Yasunori Goto
2004-06-25 20:45 ` Yasunori Goto
2004-06-25 20:49 ` Dave Hansen
2004-06-25 20:49 ` Dave Hansen
2004-06-25 20:54 ` Dave Hansen
2004-06-25 20:54 ` Dave Hansen
2004-06-25 4:49 ` [Lhms-devel] Re: [Lhns-devel] " Shai Fultheim
2004-06-25 4:49 ` Shai Fultheim
2004-06-25 15:16 ` Dave Hansen
2004-06-25 15:16 ` Dave Hansen
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=1088133541.3918.1348.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=bradc1@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=lhns-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ygoto@us.fujitsu.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 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.