[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <op.vtt1clbd3l0zgt@mnazarewicz-glaptop>
Date: Tue, 12 Apr 2011 17:58:59 +0200
From: "Michal Nazarewicz" <mina86@...a86.com>
To: "Dave Hansen" <dave@...ux.vnet.ibm.com>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, "Timur Tabi" <timur@...escale.com>,
"Andi Kleen" <andi@...stfloor.org>, "Mel Gorman" <mel@....ul.ie>,
"David Rientjes" <rientjes@...gle.com>
Subject: Re: [PATCH 2/3] make new alloc_pages_exact()
On Tue, 12 Apr 2011 17:04:13 +0200, Dave Hansen <dave@...ux.vnet.ibm.com>
wrote:
> On Tue, 2011-04-12 at 12:28 +0200, Michal Nazarewicz wrote:
>> > Dave Hansen <dave@...ux.vnet.ibm.com> wrote:
>> >> +void __free_pages_exact(struct page *page, size_t nr_pages)
>> >> +{
>> >> + struct page *end = page + nr_pages;
>> >> +
>> >> + while (page < end) {
>> >> + __free_page(page);
>> >> + page++;
>> >> + }
>> >> +}
>> >> +EXPORT_SYMBOL(__free_pages_exact);
>>
>> On Tue, 12 Apr 2011 00:22:23 +0200, Andrew Morton wrote:
>> > Really, this function duplicates release_pages().
>>
>> It requires an array of pointers to pages which is not great though if
>> one
>> just wants to free a contiguous sequence of pages.
>
> Actually, the various mem_map[]s _are_ arrays, at least up to
> MAX_ORDER_NR_PAGES at a time. We can use that property here.
In that case, waiting eagerly for the new patch. :)
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michal "mina86" Nazarewicz (o o)
ooo +-----<email/xmpp: mnazarewicz@...gle.com>-----ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists