From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: linux-mm <linux-mm@kvack.org>
Cc: LHMS <lhms-devel@lists.sourceforge.net>
Subject: [RFC] free_area[] bitmap elimination [1/3]
Date: Sat, 21 Aug 2004 11:36:58 +0900 [thread overview]
Message-ID: <4126B54A.9000206@jp.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 154 bytes --]
This patch removes bitmap initialization.
--
--the clue is these footmarks leading to the door.--
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
[-- Attachment #2: eliminate-bitmap-p02.patch --]
[-- Type: text/x-patch, Size: 1774 bytes --]
Remove bitmap initialization in free_area_init_core()
---
linux-2.6.8.1-kame-kamezawa/mm/page_alloc.c | 36 ----------------------------
1 files changed, 1 insertion(+), 35 deletions(-)
diff -puN mm/page_alloc.c~eliminate-bitmap-p02 mm/page_alloc.c
--- linux-2.6.8.1-kame/mm/page_alloc.c~eliminate-bitmap-p02 2004-08-21 08:53:20.026423144 +0900
+++ linux-2.6.8.1-kame-kamezawa/mm/page_alloc.c 2004-08-21 08:53:20.033422080 +0900
@@ -1514,42 +1514,8 @@ static void __init free_area_init_core(s
zone_start_pfn += size;
lmem_map += size;
- for (i = 0; ; i++) {
- unsigned long bitmap_size;
-
+ for (i = 0; i < MAX_ORDER ; i++) {
INIT_LIST_HEAD(&zone->free_area[i].free_list);
- if (i == MAX_ORDER-1) {
- zone->free_area[i].map = NULL;
- break;
- }
-
- /*
- * Page buddy system uses "index >> (i+1)",
- * where "index" is at most "size-1".
- *
- * The extra "+3" is to round down to byte
- * size (8 bits per byte assumption). Thus
- * we get "(size-1) >> (i+4)" as the last byte
- * we can access.
- *
- * The "+1" is because we want to round the
- * byte allocation up rather than down. So
- * we should have had a "+7" before we shifted
- * down by three. Also, we have to add one as
- * we actually _use_ the last bit (it's [0,n]
- * inclusive, not [0,n[).
- *
- * So we actually had +7+1 before we shift
- * down by 3. But (n+8) >> 3 == (n >> 3) + 1
- * (modulo overflows, which we do not have).
- *
- * Finally, we LONG_ALIGN because all bitmap
- * operations are on longs.
- */
- bitmap_size = (size-1) >> (i+4);
- bitmap_size = LONG_ALIGN(bitmap_size+1);
- zone->free_area[i].map =
- (unsigned long *) alloc_bootmem_node(pgdat, bitmap_size);
}
}
}
_
reply other threads:[~2004-08-21 2:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4126B54A.9000206@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lhms-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox