From: Dave Hansen <haveblue@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Dave Hansen <haveblue@us.ibm.com>, apw@shadowen.org
Subject: [RFC][PATCH 3/5] remove-free_all_bootmem() #define
Date: Tue, 25 Jan 2005 16:23:40 -0800 [thread overview]
Message-ID: <E1CtayD-0006sU-00@kernel.beaverton.ibm.com> (raw)
in arch/i386/mm/init.c, there's a #define for __free_all_bootmem():
#ifndef CONFIG_DISCONTIGMEM
#define __free_all_bootmem() free_all_bootmem()
#else
#define __free_all_bootmem() free_all_bootmem_node(NODE_DATA(0))
#endif /* !CONFIG_DISCONTIGMEM */
However, both of those functions end up eventuall calling the same
thing:
free_all_bootmem_core(NODE_DATA(0))
This might have once been a placeholder for a more complex bootmem
init call, but that never happened. So, kill off the DISCONTIG
version, and just call free_all_bootmem() directly in both cases.
---
memhotplug-dave/arch/i386/mm/init.c | 8 +-------
1 files changed, 1 insertion(+), 7 deletions(-)
diff -puN arch/i386/mm/init.c~A1.3-remove-free_all_bootmem-define arch/i386/mm/init.c
--- memhotplug/arch/i386/mm/init.c~A1.3-remove-free_all_bootmem-define 2005-01-25 13:59:50.000000000 -0800
+++ memhotplug-dave/arch/i386/mm/init.c 2005-01-25 14:00:14.000000000 -0800
@@ -579,12 +579,6 @@ static void __init set_max_mapnr_init(vo
#endif
}
-#ifndef CONFIG_DISCONTIGMEM
-#define __free_all_bootmem() free_all_bootmem()
-#else
-#define __free_all_bootmem() free_all_bootmem_node(NODE_DATA(0))
-#endif /* !CONFIG_DISCONTIGMEM */
-
static struct kcore_list kcore_mem, kcore_vmalloc;
void __init mem_init(void)
@@ -620,7 +614,7 @@ void __init mem_init(void)
#endif
/* this will put all low memory onto the freelists */
- totalram_pages += __free_all_bootmem();
+ totalram_pages += free_all_bootmem();
reservedpages = 0;
for (tmp = 0; tmp < max_low_pfn; tmp++)
_
--
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>
reply other threads:[~2005-01-26 0:23 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=E1CtayD-0006sU-00@kernel.beaverton.ibm.com \
--to=haveblue@us.ibm.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--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