Re: [PATCH 2/3] xvmalloc memory allocator

[Nitin Gupta]

Andrew Morton wrote:
> On Sat, 21 Mar 2009 01:13:42 +0530 Nitin Gupta <ngupta@xxxxxxxxxx> wrote:

> 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?

xvmalloc itself is completely independent of compressed-swap. Infact, its
loaded as separate kernel module (xvmalloc.ko)
However, this compression project is almost useless without this specialized
allocator.

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

I have now heard this many times and my conscious is beginning to hurt now :)
I will change it to match name of its block device: ramzswap   sounds better?

> > Anyways, I will move it to drivers/block.
>
> This sounds like it might be a backward step.


I'm bit confused here. Last thing I want to do is block mainline merge
because of such issues. Its real pain to maintain these things separately.

Thanks,
Nitin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/