[linux-mm-cc] [PATCH 0/4] compcache: in-memory compressed swapping v2
ngupta at vflare.org
Mon Sep 14 00:04:29 EDT 2009
On Mon, Sep 14, 2009 at 12:37 AM, Hugh Dickins
<hugh.dickins at tiscali.co.uk> wrote:
> On Sat, 12 Sep 2009, Nitin Gupta wrote:
>> On 09/10/2009 03:32 AM, Nitin Gupta wrote:
>> > Project home: http://compcache.googlecode.com/
>> > * Changelog: v2 vs initial revision
>> > - Use 'struct page' instead of 32-bit PFNs in ramzswap driver and
>> > xvmalloc.
>> > This is to make these 64-bit safe.
>> > - xvmalloc is no longer a separate module and does not export any symbols.
>> > Its compiled directly with ramzswap block driver. This is to avoid any
>> > last bit of confusion with any other allocator.
>> > - set_swap_free_notify() now accepts block_device as parameter instead of
>> > swp_entry_t (interface cleanup).
>> > - Fix: Make sure ramzswap disksize matches usable pages in backing swap
>> > file.
>> > This caused initialization error in case backing swap file had
>> > intra-page
>> > fragmentation.
>> Can anyone please review these patches for possible inclusion in 2.6.32?
> Sorry, I certainly wouldn't be able to review them for 2.6.32 myself.
> Since we're already in the merge window, and this work has not yet
> had exposure in mmotm (preferably) or linux-next, I really doubt
> anyone should be pushing it for 2.6.32.
> I'd be quite glad to see it and experiment with it in mmotm,
> so it could go into 2.6.33 if all okay. And I now fully accept
> that the discard/trim situation is so hazy that you are quite
> right to be asking for your own well-defined notifier instead.
> But I'm not going to pretend to have reviewed it.
Thanks for the pointer Hugh -- I will try to post patches against mmotm later.
More information about the linux-mm-cc