From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC] pearing off zone from physical memory layout [0/10]
Date: Tue, 07 Feb 2006 08:59:54 +0900 [thread overview]
Message-ID: <43E7E2FA.8010807@jp.fujitsu.com> (raw)
In-Reply-To: <1139254063.6189.97.camel@localhost.localdomain>
Dave Hansen wrote:
> On Fri, 2006-02-03 at 16:35 +0900, KAMEZAWA Hiroyuki wrote:
>> This series of patches remove members from zone, which depends on physical
>> memory layout, zone_start_pfn, spanned_pages, zone_mem_map against 2.6.16-rc1.
>>
>> By this, zone's meaning will be changed from "a range of memory to be used
>> in a same manner" to "a group of memory to be used in a same manner".
>
> This looks like pretty good stuff. I especially like that it gets rid
> of that seqlock that I had to add for memory hotplug. My only concern
> would be in the increased page_to_pfn() overhead. Any data on that?
>
I don't have any data, because I don't have a NUMA environment which needs this.
My x86 box is not NUMA and IA64 uses vmem_map, doesn't access zone->zone_mem_map.
Archs which needs test are alpha, arm, m32r, i386, parisc, x86_64.
(powerpc doesn't have DISCONTIGMEM config)
To make codes clean before asking test, I posted unify_pfn_to_page patch to lkml.
(I'll have to rewrite and repost it..)
After it goes, I'll post renewed patch as request-for-test.
sorry for Bad e-mail subject :(
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:[~2006-02-06 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 7:35 [RFC] pearing off zone from physical memory layout [0/10] KAMEZAWA Hiroyuki
2006-02-03 16:47 ` Christoph Lameter
2006-02-03 17:02 ` Kamezawa Hiroyuki
2006-02-06 19:27 ` Dave Hansen
2006-02-06 23:59 ` 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=43E7E2FA.8010807@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
/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.