public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan.kim@gmail.com>,
	Hugh Dickins <hugh.dickins@tiscali.co.uk>, Cyp <cyp561@gmail.com>,
	driverdev <devel@driverdev.osuosl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] zram: generic RAM based compressed R/W block devices
Date: Wed, 16 Jun 2010 11:43:55 -0700	[thread overview]
Message-ID: <20100616184355.GA14248@kroah.com> (raw)
In-Reply-To: <4C18337C.3040605@vflare.org>

On Wed, Jun 16, 2010 at 07:44:20AM +0530, Nitin Gupta wrote:
> Hi Greg,
> 
> On 05/28/2010 09:56 PM, Greg KH wrote:
> > On Fri, May 28, 2010 at 09:38:53PM +0530, Nitin Gupta wrote:
> >>
> >> On 05/24/2010 07:48 PM, Nitin Gupta wrote:
> >>> Creates RAM based block devices: /dev/zramX (X = 0, 1, ...).
> >>> Pages written to these disks are compressed and stored in memory
> >>> itself. These disks allow very fast I/O and compression provides
> >>> good amounts of memory savings.
> >>>
> >>> This is enhancement over existing ramzswap driver which creates
> >>> virtual block devices (/dev/ramzswapX) which could be used only
> >>> as swap disks.
> >>>
> >>> Now, with the ability to handle any kind of I/O request, zram
> >>> devices have lot more use cases:
> >>>  - /tmp storage
> >>>  - various caches under /var
> >>>  - swap disks
> >>>  - maybe even more! :)
> >>>
> >>> Performance numbers can be found at:
> >>> http://code.google.com/p/compcache/wiki/zramperf
> >>>
> >>
> >> Any reviews/comments, please?
> > 
> > We are all busy with the .35-rc1 merge work at the moment, sorry.
> > 
> 
> Can you please apply these patches to linux-next?

Yes, I'm working on it, I should get to it by the end of this week.

> or maybe for .35-rc3/rc4 too?

No, this is not a bugfix, why would it be acceptable for the .35 kernel
release?

thanks,

greg k-h

  reply	other threads:[~2010-06-16 18:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 14:18 [PATCH 0/3] zram: generic RAM based compressed R/W block devices Nitin Gupta
2010-05-24 14:18 ` [PATCH 1/3] Support generic I/O requests Nitin Gupta
2010-05-31 15:41   ` Minchan Kim
2010-05-31 19:23     ` Nitin Gupta
2010-05-24 14:18 ` [PATCH 2/3] Rename ramzswap to zram in code Nitin Gupta
2010-05-24 15:31   ` Arnd Bergmann
2010-05-24 18:23     ` Nitin Gupta
2010-05-24 14:18 ` [PATCH 3/3] Rename ramzswap to zram in documentation Nitin Gupta
2010-05-25 15:21 ` [PATCH 0/3] zram: generic RAM based compressed R/W block devices Minchan Kim
2010-05-28 16:08 ` Nitin Gupta
2010-05-28 16:26   ` Greg KH
2010-05-29  1:21     ` Nitin Gupta
2010-05-29 16:36       ` Greg KH
2010-06-16  2:14     ` Nitin Gupta
2010-06-16 18:43       ` Greg KH [this message]
2010-06-17  1:39         ` Nitin Gupta
2010-06-17 14: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=20100616184355.GA14248@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=cyp561@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan.kim@gmail.com \
    --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