From: Andrew Morton <akpm@linux-foundation.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: mm/page_alloc.c: remove hand-coded get_order()
Date: Tue, 15 Apr 2008 02:35:05 -0700 [thread overview]
Message-ID: <20080415023505.2c5eac5f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080415092317.GA1529@elf.ucw.cz>
On Tue, 15 Apr 2008 11:23:27 +0200 Pavel Machek <pavel@ucw.cz> wrote:
>
> __get_free_pages() is strange interface:
>
> It has underscores, yet get_free_pages() does not exists.
>
> It returns long when most people need pointer.
It is a bit odd.
> (And it takes order, when many people want to pass size).
>
> What about creating void *get_free_pages(flags, order) version,
Sounds sensible. It matches free_pages().
> then slowly converting users to it?
alas, poor me.
>
> ---
>
> Remove hand-coded get_order() from page_alloc.c.
>
> Signed-off-by: Pavel Machek <pavel@suse.cz>
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 402a504..c48aa45 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -4339,9 +4339,7 @@ void *__init alloc_large_system_hash(con
> else if (hashdist)
> table = __vmalloc(size, GFP_ATOMIC, PAGE_KERNEL);
> else {
> - unsigned long order;
> - for (order = 0; ((1UL << order) << PAGE_SHIFT) < size; order++)
> - ;
> + unsigned long order = get_order(size);
> table = (void*) __get_free_pages(GFP_ATOMIC, order);
> /*
> * If bucketsize is not a power-of-two, we may free
>
OK. get_order() does round up, doesn't it? We seem to have forgotten to
document that rather important detail.
next prev parent reply other threads:[~2008-04-15 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 9:23 mm/page_alloc.c: remove hand-coded get_order() Pavel Machek
2008-04-15 9:35 ` Andrew Morton [this message]
2008-04-15 9:38 ` Andrew Morton
2008-04-15 10:39 ` Andi Kleen
2008-04-16 19:18 ` Christoph Lameter
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=20080415023505.2c5eac5f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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