From: Hugh Dickins <hugh.dickins@tiscali.co.uk>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ed Tomlinson <edt@aei.ca>, Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-mm-cc <linux-mm-cc@laptop.org>
Subject: Re: [PATCH 0/4] compcache: in-memory compressed swapping v2
Date: Sun, 13 Sep 2009 20:07:05 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0909131956590.28668@sister.anvils> (raw)
In-Reply-To: <4AAB065D.3070602@vflare.org>
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.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-09-13 19:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909100215.36350.ngupta@vflare.org>
2009-09-09 21:19 ` [PATCH 2/4] virtual block device driver (ramzswap) Nitin Gupta
2009-09-14 20:10 ` Pekka Enberg
2009-09-15 6:39 ` Nitin Gupta
2009-09-15 7:30 ` Pekka Enberg
2009-09-15 8:21 ` Nitin Gupta
2009-09-15 8:30 ` Pekka Enberg
2009-09-15 15:26 ` Greg KH
2009-09-15 15:55 ` Nitin Gupta
2009-09-15 11:45 ` Ed Tomlinson
2009-09-15 12:42 ` Pekka Enberg
2009-09-15 13:14 ` Steven Rostedt
2009-09-15 13:43 ` Pekka Enberg
2009-09-15 14:08 ` Steven Rostedt
2009-09-09 21:21 ` [PATCH 4/4] documentation Nitin Gupta
2009-09-09 21:50 ` [PATCH 3/4] send callback when swap slot is freed Nitin Gupta
2009-09-09 21:53 ` [PATCH 1/4] xvmalloc memory allocator Nitin Gupta
2009-09-09 22:02 ` [PATCH 0/4] compcache: in-memory compressed swapping v2 Nitin Gupta
2009-09-12 2:24 ` Nitin Gupta
2009-09-13 19:07 ` Hugh Dickins [this message]
2009-09-14 4:04 ` Nitin Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0909131956590.28668@sister.anvils \
--to=hugh.dickins@tiscali.co.uk \
--cc=akpm@linux-foundation.org \
--cc=edt@aei.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=penberg@cs.helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox