From: Nitin Gupta <ngupta@vflare.org>
To: Greg KH <greg@kroah.com>
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: Fri, 28 May 2010 21:38:53 +0530 [thread overview]
Message-ID: <4BFFEA95.9040505@vflare.org> (raw)
In-Reply-To: <1274710685-2351-1-git-send-email-ngupta@vflare.org>
Hi All,
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?
I also performed iozone tests to stress zram:
http://code.google.com/p/compcache/wiki/zramIOzone
Note that the effect of pagecache could not be completely
avoided, even when pagecache was dropped every 1 second.
So, this iozone test should not be considered for speed
measurements but as a stress test only. For speed tests,
you can refer 'dd' test results included in changelog (patch 1).
No errors were observed during either iozone or dd tests.
Thanks,
Nitin
next prev parent reply other threads:[~2010-05-28 16:09 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 ` [PATCH 0/3] zram: generic RAM based compressed R/W block devices Minchan Kim
2010-05-28 16:08 ` Nitin Gupta [this message]
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=4BFFEA95.9040505@vflare.org \
--to=ngupta@vflare.org \
--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=minchan.kim@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
Powered by JetHome