From: Minchan Kim <minchan.kim@gmail.com>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Greg KH <greg@kroah.com>, Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
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, 26 May 2010 00:21:15 +0900 [thread overview]
Message-ID: <20100525152115.GB3227@barrios-desktop> (raw)
In-Reply-To: <1274710685-2351-1-git-send-email-ngupta@vflare.org>
Hi, Nitin.
On Mon, May 24, 2010 at 07:48:02PM +0530, 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! :)
Wow, it looks good to me.
As a matter of fact, when I saw your descriptoin, I thought we can merge
your feature into brd. But I changed my mind due to following as
First of all, ramfs supports direct I/O. So it's hard to support compression.
If we can select optionable config, it would make brd code complicated or ugly.
That's because ramzswap uses own allocator, compression, extended ioctl and so on.
And some users might regard write with important than read without considering space.
So it would be better to keep other block device for easy use and clear code.
I will review this code when I have a time.
Thanks, Nitin.
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2010-05-25 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 14:18 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 ` Minchan Kim [this message]
2010-05-28 16:08 ` [PATCH 0/3] zram: generic RAM based compressed R/W block devices 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
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=20100525152115.GB3227@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cyp561@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®