From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>,
"Luck, Tony" <tony.luck@intel.com>
Cc: LinuxIA64 <linux-ia64@vger.kernel.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC/PATCH] pfn_valid() more generic : arch independent part[0/2]
Date: Thu, 07 Oct 2004 07:38:08 -0700 [thread overview]
Message-ID: <1248570000.1097159887@[10.10.2.4]> (raw)
In-Reply-To: <4164E20D.5020400@jp.fujitsu.com>
> mem_map(1) from 36e length 1fb6d --- ZONE_DMA (36e to 1fedb)
> mem_map(2) from 1fedc length 124 --- ZONE_DMA (1fedc to 20000)
> ZONE_DMA is 0G to 4G.
> mem_map(3) from 40000 length 40000 --- ZONE_NORMAL (4G to 8G, this mem_map is aligned)
> mem_map(4) from a0000 length 20000 --- ZONE_NORMAL (10G to 12G)
> mem_map(5) from bfedc length 124 --- ZONE_NORMAL (this is involved in mem_map(4))
> ZONE_NORMAL is 4G to 12G.
>
> 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.
>
> virtual_memmap_init() is called directly from efi_memmap_walk() and
> it doesn't take granule size of ia64 into account.
>
> Hmm....
> It looks what I should do is to make memmap to be aligned to ia64's granule.
> thanks for your advise. I maybe considerd this problem too serious.
>
> If vmemmap is aligned, ia64_pfn_valid() will work fine. or only 1 level table
> will be needed.
The normal way to fix the above is just to have a bitmap array to test -
in your case a 1GB granularity would be sufficicent. That takes < 1 word
to implement for the example above ;-)
M.
--
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 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 5:22 Luck, Tony
2004-10-07 6:28 ` Hiroyuki KAMEZAWA
2004-10-07 6:51 ` align vmemmap to ia64's granule Hiroyuki KAMEZAWA
2004-10-07 14:38 ` Martin J. Bligh [this message]
2004-10-07 23:38 ` [RFC/PATCH] pfn_valid() more generic : arch independent part[0/2] Hiroyuki KAMEZAWA
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 15:53 Luck, Tony
2004-10-07 16:02 ` Martin J. Bligh
2004-10-06 6:37 Hiroyuki KAMEZAWA
2004-10-06 15:14 ` Martin J. Bligh
2004-10-07 0:10 ` Hiroyuki KAMEZAWA
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='1248570000.1097159887@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox