From: Nitin Gupta <ngupta@vflare.org>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-mm-cc@laptop.org
Subject: [PATCH 0/4] compcache: compressed in-memory swapping
Date: Mon, 24 Aug 2009 10:07:33 +0530 [thread overview]
Message-ID: <200908241007.33844.ngupta@vflare.org> (raw)
Hi,
Project home: http://compcache.googlecode.com/
It creates RAM based block devices which can be used (only) as swap disks.
Pages swapped to this device are compressed and stored in memory itself. This
is a big win over swapping to slow hard-disk which are typically used as swap
disk. For flash, these suffer from wear-leveling issues when used as swap disk
- so again its helpful. For swapless systems, it allows more apps to run for a
given amount of memory.
It can create multiple ramzswap devices (/dev/ramzswapX, X = 0, 1, 2, ...).
Each of these devices can have separate backing swap (file or disk partition)
which is used when incompressible page is found or memory limit for device is
reached.
A separate userspace utility called rzscontrol is used to manage individual
ramzswap devices.
* Testing notes
Tested on x86, x64, ARM
ARM:
- Cortex-A8 (Beagleboard)
- ARM11 (Android G1)
- OMAP2420 (Nokia N810)
* Performance
All performance numbers/plots can be found at:
http://code.google.com/p/compcache/wiki/Performance
Below is a summary of this data:
General:
- Swap R/W times are reduced from milliseconds (in case of hard disks)
down to microseconds.
Positive cases:
- Shows 33% improvement in 'scan' benchmark which allocates given amount
of memory and linearly reads/writes to this region. This benchmark also
exposes *bottlenecks* in ramzswap code (global mutex) due to which this gain
is so small.
- On Linux thin clients, it gives the effect of nearly doubling the amount of
memory.
Negative cases:
Any workload that has active working set w.r.t. filesystem cache that is
nearly equal to amount of RAM while has minimal anonymous memory requirement,
is expected to suffer maximum loss in performance with ramzswap enabled.
Iozone filesystem benchmark can simulate exactly this kind of workload.
As expected, this test shows performance loss of ~25% with ramzswap.
(Sorry for long patch[2/4] but its now very hard to split it up).
Documentation/blockdev/00-INDEX | 2 +
Documentation/blockdev/ramzswap.txt | 52 ++
drivers/block/Kconfig | 22 +
drivers/block/Makefile | 1 +
drivers/block/ramzswap/Makefile | 2 +
drivers/block/ramzswap/ramzswap.c | 1511 +++++++++++++++++++++++++++++++++
drivers/block/ramzswap/ramzswap.h | 182 ++++
drivers/block/ramzswap/xvmalloc.c | 556 ++++++++++++
drivers/block/ramzswap/xvmalloc.h | 30 +
drivers/block/ramzswap/xvmalloc_int.h | 86 ++
include/linux/ramzswap_ioctl.h | 51 ++
include/linux/swap.h | 5 +
mm/swapfile.c | 33 +
13 files changed, 2533 insertions(+), 0 deletions(-)
--
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 reply other threads:[~2009-08-26 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 4:37 Nitin Gupta [this message]
2009-08-24 16:01 ` Randy Dunlap
2009-08-24 17:30 ` 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=200908241007.33844.ngupta@vflare.org \
--to=ngupta@vflare.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=linux-mm@kvack.org \
/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