[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <000c01cc2769$02669b70$0733d250$%szyprowski@samsung.com>
Date: Fri, 10 Jun 2011 14:22:05 +0200
From: Marek Szyprowski <m.szyprowski@...sung.com>
To: 'Alan Cox' <alan@...rguk.ukuu.org.uk>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-media@...r.kernel.org, linux-mm@...ck.org,
linaro-mm-sig@...ts.linaro.org,
'Michal Nazarewicz' <mina86@...a86.com>,
'Kyungmin Park' <kyungmin.park@...sung.com>,
'Andrew Morton' <akpm@...ux-foundation.org>,
'KAMEZAWA Hiroyuki' <kamezawa.hiroyu@...fujitsu.com>,
'Ankita Garg' <ankita@...ibm.com>,
'Daniel Walker' <dwalker@...eaurora.org>,
'Johan MOSSBERG' <johan.xx.mossberg@...ricsson.com>,
'Mel Gorman' <mel@....ul.ie>, 'Arnd Bergmann' <arnd@...db.de>,
'Jesse Barker' <jesse.barker@...aro.org>
Subject: RE: [PATCH 02/10] lib: genalloc: Generic allocator improvements
Hello,
On Friday, June 10, 2011 1:25 PM Alan Cox wrote:
> I am curious about one thing
>
> Why do we need this allocator. Why not use allocate_resource and friends.
> The kernel generic resource handler already handles object alignment and
> subranges. It just seems to be a surplus allocator that could perhaps be
> mostly removed by using the kernel resource allocator we already have ?
genalloc was used mainly for historical reasons (in the earlier version we
were looking for direct replacement for first fit allocator).
I plan to replace it with lib/bitmap.c bitmap_* based allocator (similar like
it it is used by dma_declare_coherent_memory() and friends in
drivers/base/dma-coherent.c). We need something really simple for CMA area
management.
IMHO allocate_resource and friends a bit too heavy here, but good to know
that such allocator also exists.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
--
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