From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] modifing vmemmap initialization [1/1] : modifies init
Date: Wed, 22 Dec 2004 01:16:37 +0000 [thread overview]
Message-ID: <41C8CAF5.1060902@jp.fujitsu.com> (raw)
In-Reply-To: <41C7CC9E.7080602@jp.fujitsu.com>
Matthew Wilcox wrote:
>>>This patch adjust calling sequence of virtual_mem_map_alloc(),
>>>which is added by previous patch.
>>
>>This doesn't look like an improvement at all, the whole virtual memmap
>>should not need core ifdefs. In fact I still hope it'll go away.
>
>
> It doesn't need core ifdefs at all -- simply define a dummy
> virtual_mem_map_alloc() and you can remove the ifdefs.
>
I'm thinking about pass "memmap allocation function" as a free_area_init_node()'s argument.
Such args can be used in i386(or some) NUMA case, which doesn't use alloc_bootmem().
Anyway, my patch is not good.
> (I also hope it'll go away. Where's CONFIG_NONLINEAR got to?)
>
Robert Picco's one was intended to avoid using CONFIG_VIRTUAL_MEM_MAP.
I wrote another one, which uses CONFIG_VIRTUAL_MEM_MAP, and it was too complicated :(
-- Kame <kamezawa.hiroyu@jp.fujitsu.com>
prev parent reply other threads:[~2004-12-22 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 7:11 [PATCH] modifing vmemmap initialization [0/1] : move vmemmap creation Hiroyuki KAMEZAWA
2004-12-21 7:20 ` [PATCH] modifing vmemmap initialization [1/1] : modifies init sequence Hiroyuki KAMEZAWA
2004-12-21 18:33 ` Christoph Hellwig
2004-12-21 18:39 ` Matthew Wilcox
2004-12-22 1:16 ` Hiroyuki KAMEZAWA [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=41C8CAF5.1060902@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox