From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Timur Tabi <timur@freescale.com>
Cc: linux-kernel@vger.kernel.org, andi@firstfloor.org,
randy.dunlap@oracle.com, corbet@lwn.net,
torvalds@linux-foundation.org
Subject: Re: [PATCH] Add alloc_pages_exact() and free_pages_exact()
Date: Tue, 24 Jun 2008 14:33:38 -0700 [thread overview]
Message-ID: <1214343218.12367.58.camel@nimitz> (raw)
In-Reply-To: <1214325649-26075-1-git-send-email-timur@freescale.com>
On Tue, 2008-06-24 at 11:40 -0500, Timur Tabi wrote:
> +void *alloc_pages_exact(size_t size, gfp_t gfp_mask)
> +{
> + unsigned int order = get_order(size);
> + unsigned long addr;
> +
> + addr = __get_free_pages(gfp_mask, order);
> + if (addr) {
> + unsigned long alloc_end = addr + (PAGE_SIZE << order);
> + unsigned long used = addr + PAGE_ALIGN(size);
> +
> + split_page(virt_to_page(addr), order);
> + while (used < alloc_end) {
> + free_page(used);
> + used += PAGE_SIZE;
> + }
> + }
> +
> + return (void *)addr;
> +}
Hi Timur,
This looks like a really good idea. It looks pretty good to me, no
functional problems. My brain had a really hard time parsing that code
for some reason, though. Could just be a lack of coffee.
I think the thing that confused me was trying to figure out if
'alloc_end' was the end of what we *did* allocate from
__get_free_pages() or if it was the *goal* allocation end.
'used' also seemed like a slightly strange variable name because it
points to the memory which is about to be freed and ends up *unused*.
I'll offer this up just in case you like it better. For me, it is
easier to parse, and should do the exact same thing. I also think it's
slightly nicer to do the arithmetic on 'struct page *' rather than
vaddrs in 'unsigned long'. It is _slightly_ cheaper not having to do a
virt_to_page() on each free_page() call. The same would go for the free
side as well.
All of the 'struct page *' arithmetic is OK since it is all done inside
one MAX_ORDER area.
void *alloc_pages_exact(size_t size, gfp_t gfp_mask)
{
unsigned int order = get_order(size);
void *alloc;
struct page *surplus_start;
struct page *surplus_end;
struct page *page;
size = PAGE_ALIGN(size);
alloc = (void *)__get_free_pages(gfp_mask, order);
if (!alloc)
return NULL;
/* Turn the big allocation into a bunch of single pages */
split_page(virt_to_page(alloc), order);
surplus_start = virt_to_page(alloc + size);
surplus_end = surplus_start + (1 << order);
for (page = surplus_start; page < surplus_end; page++)
__free_page(page);
return alloc;
}
-- Dave
next prev parent reply other threads:[~2008-06-24 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 16:40 [PATCH] Add alloc_pages_exact() and free_pages_exact() Timur Tabi
2008-06-24 21:33 ` Dave Hansen [this message]
2008-06-24 21:44 ` Timur Tabi
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=1214343218.12367.58.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=andi@firstfloor.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=timur@freescale.com \
--cc=torvalds@linux-foundation.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