From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>
Cc: wli@holomorphy.com, linux-mm@kvack.org, lhms-devel@lists.sourceforge.net
Subject: Re: [Lhms-devel] Re: [RFC] free_area[] bitmap elimination [0/3]
Date: Sat, 21 Aug 2004 14:26:48 +0900 [thread overview]
Message-ID: <4126DD18.70306@jp.fujitsu.com> (raw)
In-Reply-To: <20040821.140121.41645060.taka@valinux.co.jp>
Hi,
Hirokazu Takahashi wrote:
> Hi,
>
>
>>William Lee Irwin III wrote:
>>
>>
>>>On Sat, Aug 21, 2004 at 11:31:21AM +0900, Hiroyuki KAMEZAWA wrote:
>>>
>>>
>>>>This patch removes bitmap from buddy allocator used in
>>>>alloc_pages()/free_pages() in the kernel 2.6.8.1.
<snip>
>>In my understanding, the patch assumes that size of mem_map[] in each
>>zone must be multiple of 2^MAX_ORDER, right?
>>But it doesn't seem it's a big problem, as we can just allocate extra
>>mem_map[] to round up if it isn't.
>
>
> I think this may help the buddy allocator to work withtout adding
> page_ivs_valid(buddy1).
>
>
As you say, I expects the size of zone is multiple of MAX_ORDER.
But IA64 kernel's MAX_ORDER is 4 Giga bytes :(
A Tiger4, an IA64 machine, I use has physical memory map like this:
0-2G :
4-8G :
10-12G:
contiguous mem_map is smaller than MAX_ORDER.
So I think page_is_valid(buddy1) is needed only for a few pages,
which is top of big buddy, in this case.
Hmm.... :(
Thank you,
KAME
--
--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-08-21 5:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 2:31 Hiroyuki KAMEZAWA
2004-08-21 2:55 ` William Lee Irwin III
2004-08-21 4:56 ` [Lhms-devel] " Hirokazu Takahashi
2004-08-21 5:21 ` William Lee Irwin III
2004-08-21 5:37 ` Hiroyuki KAMEZAWA
2004-08-21 5:37 ` William Lee Irwin III
2004-08-21 6:10 ` Hiroyuki KAMEZAWA
2004-08-21 17:48 ` William Lee Irwin III
2004-08-21 5:00 ` Hiroyuki KAMEZAWA
2004-08-21 5:01 ` [Lhms-devel] " Hirokazu Takahashi
2004-08-21 5:26 ` Hiroyuki KAMEZAWA [this message]
2004-08-21 5:01 ` William Lee Irwin III
2004-08-21 9:43 ` Nigel Cunningham
2004-08-23 14:36 ` [Lhms-devel] " Dave Hansen
2004-08-23 15:00 ` Dave Hansen
2004-08-24 0:07 ` [Lhms-devel] " Hiroyuki KAMEZAWA
2004-08-24 0:00 ` [Lhms-devel] " Hiroyuki KAMEZAWA
2004-08-24 2:28 ` Hirokazu Takahashi
2004-08-24 2:49 ` Dave Hansen
2004-08-24 3:31 ` Hiroyuki KAMEZAWA
2004-08-23 15:43 ` Dave Hansen
2004-08-24 0:15 ` 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=4126DD18.70306@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=taka@valinux.co.jp \
--cc=wli@holomorphy.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