From: Nitin Gupta <ngupta@vflare.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Marcin Slusarz <marcin.slusarz@gmail.com>,
Ed Tomlinson <edt@aei.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-mm-cc <linux-mm-cc@laptop.org>
Subject: Re: [PATCH 0/3] compcache: in-memory compressed swapping v4
Date: Tue, 22 Sep 2009 14:06:12 +0530 [thread overview]
Message-ID: <d760cf2d0909220136g38c0541bxab93f9b5a2b22d7@mail.gmail.com> (raw)
In-Reply-To: <1253600030.30406.2.camel@penberg-laptop>
On Tue, Sep 22, 2009 at 11:43 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Tue, 2009-09-22 at 10:26 +0530, Nitin Gupta wrote:
>> drivers/staging/Kconfig | 2 +
>> drivers/staging/Makefile | 1 +
>> drivers/staging/ramzswap/Kconfig | 21 +
>> drivers/staging/ramzswap/Makefile | 3 +
>> drivers/staging/ramzswap/ramzswap.txt | 51 +
>> drivers/staging/ramzswap/ramzswap_drv.c | 1462 +++++++++++++++++++++++++++++
>> drivers/staging/ramzswap/ramzswap_drv.h | 173 ++++
>> drivers/staging/ramzswap/ramzswap_ioctl.h | 50 +
>> drivers/staging/ramzswap/xvmalloc.c | 533 +++++++++++
>> drivers/staging/ramzswap/xvmalloc.h | 30 +
>> drivers/staging/ramzswap/xvmalloc_int.h | 86 ++
>> include/linux/swap.h | 5 +
>> mm/swapfile.c | 34 +
>> 13 files changed, 2451 insertions(+), 0 deletions(-)
>
> This diffstat is not up to date, I think.
>
Oh! this is from v3. I forgot to update it. I don't have access to my git tree
here in office, so cannot send updated version right now.
> Greg, would you mind taking this driver into staging? There are some
> issues that need to be ironed out for it to be merged to kernel proper
> but I think it would benefit from being exposed to mainline.
>
> Nitin, you probably should also submit a patch that adds a TODO file
> similar to other staging drivers to remind us that swap notifiers and
> the CONFIG_ARM thing need to be resolved.
>
ok, I will send patch for TODO file.
Thanks,
Nitin
--
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-22 8:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 4:56 [PATCH 0/3] compcache: in-memory compressed swapping v4 Nitin Gupta
2009-09-22 4:56 ` [PATCH 1/3] xvmalloc memory allocator Nitin Gupta
2009-09-22 4:56 ` [PATCH 2/3] virtual block device driver (ramzswap) Nitin Gupta
2009-09-24 5:11 ` KAMEZAWA Hiroyuki
2009-09-24 16:54 ` Nitin Gupta
2009-09-24 23:46 ` KAMEZAWA Hiroyuki
2009-09-22 4:56 ` [PATCH 3/3] documentation Nitin Gupta
2009-10-08 22:57 ` Greg KH
2009-10-08 22:58 ` Greg KH
2009-09-22 6:13 ` [PATCH 0/3] compcache: in-memory compressed swapping v4 Pekka Enberg
2009-09-22 8:36 ` Nitin Gupta [this message]
2009-09-22 15:37 ` Greg KH
2009-09-22 15:52 ` Nitin Gupta
2009-09-23 0:40 ` Greg KH
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=d760cf2d0909220136g38c0541bxab93f9b5a2b22d7@mail.gmail.com \
--to=ngupta@vflare.org \
--cc=akpm@linux-foundation.org \
--cc=edt@aei.ca \
--cc=greg@kroah.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=linux-mm@kvack.org \
--cc=marcin.slusarz@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).