[lkml]   [2009]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/3] xvmalloc memory allocator
On Sat, 21 Mar 2009 01:13:42 +0530 Nitin Gupta <> wrote:

> Pekka Enberg wrote:
> > On 3/20/2009, "Christoph Lameter" <> wrote:
> >>> I think, with a bit playing around with interfaces, it can be turned into
> >>> general purpose allocator (this will most probably lack highmem support).
> >> Then it would need to implement the SLAB api (see include/linux/slab.h).
> >> Thus we are getting slab allocator #5.
> >
> > I do not see the point in that. As I suggested earlier, you should
> > probably just move this into drivers/block/ and make it a private
> > compcache allocator.
> >
> Your wish. But, really, we should not dismiss an O(1) allocator with great
> space-efficiency so easily. I think it will be great at least for embedded
> devices (its counterpart, SLOB is simply funny).
> Just to add to this, Xen recently included a variant of TLSF allocator
> which was used in earlier versions of compcache. TLSF is allocator on
> which xvmalloc is based.
> (Though I do not know which parts of xen depend on this allocator).
> and xvmalloc vs tlsf arguments are here:
> tlsf:

Well, xvmalloc may or may not be a good thing and we can discuss that

But what is regrettable is that xvmalloc appears to be tied to
compressed-swap in some manner. Is it not possible to split these two
initiatives apart so that neither is dependent upon the other? Or is
compressed-swap hopelessly crippled without xvmalloc?

(compcache is a terrible name, btw - it isn't a "compressed cache" at all!)

> Anyways, I will move it to drivers/block.

This sounds like it might be a backward step.

 \ /
  Last update: 2009-03-21 11:31    [W:0.059 / U:5.980 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site