Messages in this thread | | | Date | Mon, 8 Apr 2013 09:32:38 -0700 (PDT) | From | Dan Magenheimer <> | Subject | zsmalloc defrag (Was: [PATCH] mm: remove compressed copy from zram in-memory) |
| |
> From: Minchan Kim [mailto:minchan@kernel.org] > Sent: Monday, April 08, 2013 12:01 AM > Subject: [PATCH] mm: remove compressed copy from zram in-memory
(patch removed)
> Fragment ratio is almost same but memory consumption and compile time > is better. I am working to add defragment function of zsmalloc.
Hi Minchan --
I would be very interested in your design thoughts on how you plan to add defragmentation for zsmalloc. In particular, I am wondering if your design will also handle the requirements for zcache (especially for cleancache pages) and perhaps also for ramster.
In https://lkml.org/lkml/2013/3/27/501 I suggested it would be good to work together on a common design, but you didn't reply. Are you thinking that zsmalloc improvements should focus only on zram, in which case we may -- and possibly should -- end up with a different allocator for frontswap-based/cleancache-based compression in zcache (and possibly zswap)?
I'm just trying to determine if I should proceed separately with my design (with Bob Liu, who expressed interest) or if it would be beneficial to work together.
Thanks, Dan
| |