[PATCH 0/3] ramzswap: Eliminate stale data from compressed memory (v2)
Pekka Enberg
penberg at cs.helsinki.fi
Sat May 8 00:26:03 PDT 2010
Nitin Gupta wrote:
> Oops, missed this part:
>
> On 05/08/2010 11:59 AM, Pekka Enberg wrote:
>> Andrew Morton wrote:
>>> I've completely forgotten why we need this xvmalloc thing and I don't
>>> recall whether we decided it would be a good thing to have as a generic
>>> facility and of course it's all unexplained and undocumented. I won't
>>> be looking at it today, for this reason.
>> We need it because the slab allocator is not a good fit for this special
>> purpose driver due to fragmentation. Nitin, you had a nice web page
>> showing all the relevant numbers but I can't find it anymore.
>>
>
> xvmalloc performance numbers:
> http://code.google.com/p/compcache/wiki/xvMalloc
> http://code.google.com/p/compcache/wiki/xvMallocPerformance
I don't see the xvmalloc vs. kmalloc fragmentation numbers there. I
thought you had some?
More information about the devel
mailing list