From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
LinuxIA64 <linux-ia64@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: align vmemmap to ia64's granule
Date: Thu, 07 Oct 2004 15:51:15 +0900 [thread overview]
Message-ID: <4164E763.8020003@jp.fujitsu.com> (raw)
In-Reply-To: <4164E20D.5020400@jp.fujitsu.com>
Hi, Tony
This patch make vmemmap to be aligned with ia64's granule size, against 2.6.9-rc3.
Please apply this, if vmemmap is expected to be aligned with the granule size.
Kame <kamezawa.hiroyu@jp.fujitsu.com>
Hiroyuki KAMEZAWA wrote:
> Hi,
> Luck, Tony wrote:
>
>>> Because pfn_valid() often returns 0 in inner loop of free_pages_bulk(),
>>> I want to avoid page fault caused by using get_user() in pfn_valid().
>>
>>
>>
>> How often? Surely this is only a problem at the edges of blocks
>> of memory? I suppose it depends on whether your discontig memory
>> appears in blocks much smaller than MAXORDER. But even there it
>> should only be an issue coalescing buddies that are bigger than
>> the granule size (since all of the pages in a granule on ia64 are
>> guaranteed to exist, the buddy of any page must also exist).
> node's start_pfn and end_pfn is aligned to granule size, but holes in
> memmap is not.
> The vmemmap is aligned to # of page structs in one page.
---
test-kernel-kamezawa/arch/ia64/mm/init.c | 2 ++
1 files changed, 2 insertions(+)
diff -puN arch/ia64/mm/init.c~vmemmap_align_granule arch/ia64/mm/init.c
--- test-kernel/arch/ia64/mm/init.c~vmemmap_align_granule 2004-10-07 15:24:08.322733968 +0900
+++ test-kernel-kamezawa/arch/ia64/mm/init.c 2004-10-07 15:30:58.623358792 +0900
@@ -411,6 +411,8 @@ virtual_memmap_init (u64 start, u64 end,
args = (struct memmap_init_callback_data *) arg;
+ start = GRANULEROUNDDOWN(start);
+ end = GRANULEROUNDUP(end);
map_start = vmem_map + (__pa(start) >> PAGE_SHIFT);
map_end = vmem_map + (__pa(end) >> PAGE_SHIFT);
_
--
--the clue is these footmarks leading to the door.--
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
--
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-10-07 6:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 6:20 [RFC/PATCH] pfn_valid() more generic : intro[0/2] Hiroyuki KAMEZAWA
2004-10-06 6:20 ` Hiroyuki KAMEZAWA
2004-10-06 6:33 ` Luck, Tony
2004-10-06 6:33 ` Luck, Tony
2004-10-06 7:33 ` Hiroyuki KAMEZAWA
2004-10-06 7:33 ` Hiroyuki KAMEZAWA
2004-10-06 6:37 ` [RFC/PATCH] pfn_valid() more generic : arch independent part[0/2] Hiroyuki KAMEZAWA
2004-10-06 6:37 ` Hiroyuki KAMEZAWA
2004-10-06 15:14 ` Martin J. Bligh
2004-10-06 15:14 ` Martin J. Bligh
2004-10-07 0:10 ` Hiroyuki KAMEZAWA
2004-10-07 0:10 ` Hiroyuki KAMEZAWA
2004-10-07 5:22 ` Luck, Tony
2004-10-07 5:22 ` Luck, Tony
2004-10-07 6:28 ` Hiroyuki KAMEZAWA
2004-10-07 6:28 ` Hiroyuki KAMEZAWA
2004-10-07 6:51 ` Hiroyuki KAMEZAWA [this message]
2004-10-07 14:38 ` Martin J. Bligh
2004-10-07 14:38 ` Martin J. Bligh
2004-10-07 23:38 ` Hiroyuki KAMEZAWA
2004-10-07 23:38 ` Hiroyuki KAMEZAWA
2004-10-07 15:53 ` Luck, Tony
2004-10-07 15:53 ` Luck, Tony
2004-10-07 16:02 ` Martin J. Bligh
2004-10-07 16:02 ` Martin J. Bligh
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=4164E763.8020003@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=tony.luck@intel.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.