2010-06-01 08:01:26 +00:00
|
|
|
zram: Compressed RAM based block devices
|
|
|
|
----------------------------------------
|
2009-09-22 04:56:54 +00:00
|
|
|
|
|
|
|
* Introduction
|
|
|
|
|
2010-08-09 17:26:55 +00:00
|
|
|
The zram module creates RAM based block devices named /dev/zram<id>
|
|
|
|
(<id> = 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. Some of the usecases include /tmp storage,
|
|
|
|
use as swap disks, various caches under /var and maybe many more :)
|
2009-09-22 04:56:54 +00:00
|
|
|
|
2010-08-09 17:26:55 +00:00
|
|
|
Statistics for individual zram devices are exported through sysfs nodes at
|
|
|
|
/sys/block/zram<id>/
|
2009-09-22 04:56:54 +00:00
|
|
|
|
|
|
|
* Usage
|
|
|
|
|
2010-06-01 08:01:26 +00:00
|
|
|
Following shows a typical sequence of steps for using zram.
|
2009-09-22 04:56:54 +00:00
|
|
|
|
2010-08-09 17:26:55 +00:00
|
|
|
1) Load Module:
|
2010-06-01 08:01:26 +00:00
|
|
|
modprobe zram num_devices=4
|
2010-08-09 17:26:55 +00:00
|
|
|
This creates 4 devices: /dev/zram{0,1,2,3}
|
2009-09-22 04:56:54 +00:00
|
|
|
(num_devices parameter is optional. Default: 1)
|
|
|
|
|
zram: add multi stream functionality
Existing zram (zcomp) implementation has only one compression stream
(buffer and algorithm private part), so in order to prevent data
corruption only one write (compress operation) can use this compression
stream, forcing all concurrent write operations to wait for stream lock
to be released. This patch changes zcomp to keep a compression streams
list of user-defined size (via sysfs device attr). Each write operation
still exclusively holds compression stream, the difference is that we
can have N write operations (depending on size of streams list)
executing in parallel. See TEST section later in commit message for
performance data.
Introduce struct zcomp_strm_multi and a set of functions to manage
zcomp_strm stream access. zcomp_strm_multi has a list of idle
zcomp_strm structs, spinlock to protect idle list and wait queue, making
it possible to perform parallel compressions.
The following set of functions added:
- zcomp_strm_multi_find()/zcomp_strm_multi_release()
find and release a compression stream, implement required locking
- zcomp_strm_multi_create()/zcomp_strm_multi_destroy()
create and destroy zcomp_strm_multi
zcomp ->strm_find() and ->strm_release() callbacks are set during
initialisation to zcomp_strm_multi_find()/zcomp_strm_multi_release()
correspondingly.
Each time zcomp issues a zcomp_strm_multi_find() call, the following set
of operations performed:
- spin lock strm_lock
- if idle list is not empty, remove zcomp_strm from idle list, spin
unlock and return zcomp stream pointer to caller
- if idle list is empty, current adds itself to wait queue. it will be
awaken by zcomp_strm_multi_release() caller.
zcomp_strm_multi_release():
- spin lock strm_lock
- add zcomp stream to idle list
- spin unlock, wake up sleeper
Minchan Kim reported that spinlock-based locking scheme has demonstrated
a severe perfomance regression for single compression stream case,
comparing to mutex-based (see https://lkml.org/lkml/2014/2/18/16)
base spinlock mutex
==Initial write ==Initial write ==Initial write
records: 5 records: 5 records: 5
avg: 1642424.35 avg: 699610.40 avg: 1655583.71
std: 39890.95(2.43%) std: 232014.19(33.16%) std: 52293.96
max: 1690170.94 max: 1163473.45 max: 1697164.75
min: 1568669.52 min: 573429.88 min: 1553410.23
==Rewrite ==Rewrite ==Rewrite
records: 5 records: 5 records: 5
avg: 1611775.39 avg: 501406.64 avg: 1684419.11
std: 17144.58(1.06%) std: 15354.41(3.06%) std: 18367.42
max: 1641800.95 max: 531356.78 max: 1706445.84
min: 1593515.27 min: 488817.78 min: 1655335.73
When only one compression stream available, mutex with spin on owner
tends to perform much better than frequent wait_event()/wake_up(). This
is why single stream implemented as a special case with mutex locking.
Introduce and document zram device attribute max_comp_streams. This
attr shows and stores current zcomp's max number of zcomp streams
(max_strm). Extend zcomp's zcomp_create() with `max_strm' parameter.
`max_strm' limits the number of zcomp_strm structs in compression
backend's idle list (max_comp_streams).
max_comp_streams used during initialisation as follows:
-- passing to zcomp_create() max_strm equals to 1 will initialise zcomp
using single compression stream zcomp_strm_single (mutex-based locking).
-- passing to zcomp_create() max_strm greater than 1 will initialise zcomp
using multi compression stream zcomp_strm_multi (spinlock-based locking).
default max_comp_streams value is 1, meaning that zram with single stream
will be initialised.
Later patch will introduce configuration knob to change max_comp_streams
on already initialised and used zcomp.
TEST
iozone -t 3 -R -r 16K -s 60M -I +Z
test base 1 strm (mutex) 3 strm (spinlock)
-----------------------------------------------------------------------
Initial write 589286.78 583518.39 718011.05
Rewrite 604837.97 596776.38 1515125.72
Random write 584120.11 595714.58 1388850.25
Pwrite 535731.17 541117.38 739295.27
Fwrite 1418083.88 1478612.72 1484927.06
Usage example:
set max_comp_streams to 4
echo 4 > /sys/block/zram0/max_comp_streams
show current max_comp_streams (default value is 1).
cat /sys/block/zram0/max_comp_streams
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Acked-by: Minchan Kim <minchan@kernel.org>
Cc: Jerome Marchand <jmarchan@redhat.com>
Cc: Nitin Gupta <ngupta@vflare.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-04-07 22:38:14 +00:00
|
|
|
2) Set max number of compression streams
|
|
|
|
Compression backend may use up to max_comp_streams compression streams,
|
|
|
|
thus allowing up to max_comp_streams concurrent compression operations.
|
|
|
|
By default, compression backend uses single compression stream.
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
#show max compression streams number
|
|
|
|
cat /sys/block/zram0/max_comp_streams
|
|
|
|
|
|
|
|
#set max compression streams number to 3
|
|
|
|
echo 3 > /sys/block/zram0/max_comp_streams
|
|
|
|
|
|
|
|
Note:
|
|
|
|
In order to enable compression backend's multi stream support max_comp_streams
|
|
|
|
must be initially set to desired concurrency level before ZRAM device
|
|
|
|
initialisation. Once the device initialised as a single stream compression
|
2014-04-07 22:38:21 +00:00
|
|
|
backend (max_comp_streams equals to 1), you will see error if you try to change
|
|
|
|
the value of max_comp_streams because single stream compression backend
|
|
|
|
implemented as a special case by lock overhead issue and does not support
|
|
|
|
dynamic max_comp_streams. Only multi stream backend supports dynamic
|
|
|
|
max_comp_streams adjustment.
|
zram: add multi stream functionality
Existing zram (zcomp) implementation has only one compression stream
(buffer and algorithm private part), so in order to prevent data
corruption only one write (compress operation) can use this compression
stream, forcing all concurrent write operations to wait for stream lock
to be released. This patch changes zcomp to keep a compression streams
list of user-defined size (via sysfs device attr). Each write operation
still exclusively holds compression stream, the difference is that we
can have N write operations (depending on size of streams list)
executing in parallel. See TEST section later in commit message for
performance data.
Introduce struct zcomp_strm_multi and a set of functions to manage
zcomp_strm stream access. zcomp_strm_multi has a list of idle
zcomp_strm structs, spinlock to protect idle list and wait queue, making
it possible to perform parallel compressions.
The following set of functions added:
- zcomp_strm_multi_find()/zcomp_strm_multi_release()
find and release a compression stream, implement required locking
- zcomp_strm_multi_create()/zcomp_strm_multi_destroy()
create and destroy zcomp_strm_multi
zcomp ->strm_find() and ->strm_release() callbacks are set during
initialisation to zcomp_strm_multi_find()/zcomp_strm_multi_release()
correspondingly.
Each time zcomp issues a zcomp_strm_multi_find() call, the following set
of operations performed:
- spin lock strm_lock
- if idle list is not empty, remove zcomp_strm from idle list, spin
unlock and return zcomp stream pointer to caller
- if idle list is empty, current adds itself to wait queue. it will be
awaken by zcomp_strm_multi_release() caller.
zcomp_strm_multi_release():
- spin lock strm_lock
- add zcomp stream to idle list
- spin unlock, wake up sleeper
Minchan Kim reported that spinlock-based locking scheme has demonstrated
a severe perfomance regression for single compression stream case,
comparing to mutex-based (see https://lkml.org/lkml/2014/2/18/16)
base spinlock mutex
==Initial write ==Initial write ==Initial write
records: 5 records: 5 records: 5
avg: 1642424.35 avg: 699610.40 avg: 1655583.71
std: 39890.95(2.43%) std: 232014.19(33.16%) std: 52293.96
max: 1690170.94 max: 1163473.45 max: 1697164.75
min: 1568669.52 min: 573429.88 min: 1553410.23
==Rewrite ==Rewrite ==Rewrite
records: 5 records: 5 records: 5
avg: 1611775.39 avg: 501406.64 avg: 1684419.11
std: 17144.58(1.06%) std: 15354.41(3.06%) std: 18367.42
max: 1641800.95 max: 531356.78 max: 1706445.84
min: 1593515.27 min: 488817.78 min: 1655335.73
When only one compression stream available, mutex with spin on owner
tends to perform much better than frequent wait_event()/wake_up(). This
is why single stream implemented as a special case with mutex locking.
Introduce and document zram device attribute max_comp_streams. This
attr shows and stores current zcomp's max number of zcomp streams
(max_strm). Extend zcomp's zcomp_create() with `max_strm' parameter.
`max_strm' limits the number of zcomp_strm structs in compression
backend's idle list (max_comp_streams).
max_comp_streams used during initialisation as follows:
-- passing to zcomp_create() max_strm equals to 1 will initialise zcomp
using single compression stream zcomp_strm_single (mutex-based locking).
-- passing to zcomp_create() max_strm greater than 1 will initialise zcomp
using multi compression stream zcomp_strm_multi (spinlock-based locking).
default max_comp_streams value is 1, meaning that zram with single stream
will be initialised.
Later patch will introduce configuration knob to change max_comp_streams
on already initialised and used zcomp.
TEST
iozone -t 3 -R -r 16K -s 60M -I +Z
test base 1 strm (mutex) 3 strm (spinlock)
-----------------------------------------------------------------------
Initial write 589286.78 583518.39 718011.05
Rewrite 604837.97 596776.38 1515125.72
Random write 584120.11 595714.58 1388850.25
Pwrite 535731.17 541117.38 739295.27
Fwrite 1418083.88 1478612.72 1484927.06
Usage example:
set max_comp_streams to 4
echo 4 > /sys/block/zram0/max_comp_streams
show current max_comp_streams (default value is 1).
cat /sys/block/zram0/max_comp_streams
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Acked-by: Minchan Kim <minchan@kernel.org>
Cc: Jerome Marchand <jmarchan@redhat.com>
Cc: Nitin Gupta <ngupta@vflare.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-04-07 22:38:14 +00:00
|
|
|
|
2014-04-07 22:38:17 +00:00
|
|
|
3) Select compression algorithm
|
|
|
|
Using comp_algorithm device attribute one can see available and
|
|
|
|
currently selected (shown in square brackets) compression algortithms,
|
|
|
|
change selected compression algorithm (once the device is initialised
|
|
|
|
there is no way to change compression algorithm).
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
#show supported compression algorithms
|
|
|
|
cat /sys/block/zram0/comp_algorithm
|
|
|
|
lzo [lz4]
|
|
|
|
|
|
|
|
#select lzo compression algorithm
|
|
|
|
echo lzo > /sys/block/zram0/comp_algorithm
|
|
|
|
|
|
|
|
4) Set Disksize
|
2013-01-30 02:41:40 +00:00
|
|
|
Set disk size by writing the value to sysfs node 'disksize'.
|
|
|
|
The value can be either in bytes or you can use mem suffixes.
|
|
|
|
Examples:
|
|
|
|
# Initialize /dev/zram0 with 50MB disksize
|
|
|
|
echo $((50*1024*1024)) > /sys/block/zram0/disksize
|
|
|
|
|
|
|
|
# Using mem suffixes
|
|
|
|
echo 256K > /sys/block/zram0/disksize
|
|
|
|
echo 512M > /sys/block/zram0/disksize
|
|
|
|
echo 1G > /sys/block/zram0/disksize
|
2009-09-22 04:56:54 +00:00
|
|
|
|
2014-04-07 22:38:07 +00:00
|
|
|
Note:
|
|
|
|
There is little point creating a zram of greater than twice the size of memory
|
|
|
|
since we expect a 2:1 compression ratio. Note that zram uses about 0.1% of the
|
|
|
|
size of the disk when not in use so a huge zram is wasteful.
|
|
|
|
|
2014-10-09 22:29:53 +00:00
|
|
|
5) Set memory limit: Optional
|
|
|
|
Set memory limit by writing the value to sysfs node 'mem_limit'.
|
|
|
|
The value can be either in bytes or you can use mem suffixes.
|
|
|
|
In addition, you could change the value in runtime.
|
|
|
|
Examples:
|
|
|
|
# limit /dev/zram0 with 50MB memory
|
|
|
|
echo $((50*1024*1024)) > /sys/block/zram0/mem_limit
|
|
|
|
|
|
|
|
# Using mem suffixes
|
|
|
|
echo 256K > /sys/block/zram0/mem_limit
|
|
|
|
echo 512M > /sys/block/zram0/mem_limit
|
|
|
|
echo 1G > /sys/block/zram0/mem_limit
|
|
|
|
|
|
|
|
# To disable memory limit
|
|
|
|
echo 0 > /sys/block/zram0/mem_limit
|
|
|
|
|
|
|
|
6) Activate:
|
2010-06-01 08:01:26 +00:00
|
|
|
mkswap /dev/zram0
|
|
|
|
swapon /dev/zram0
|
|
|
|
|
|
|
|
mkfs.ext4 /dev/zram1
|
|
|
|
mount /dev/zram1 /tmp
|
2009-09-22 04:56:54 +00:00
|
|
|
|
2014-10-09 22:29:53 +00:00
|
|
|
7) Stats:
|
2010-08-09 17:26:55 +00:00
|
|
|
Per-device statistics are exported as various nodes under
|
|
|
|
/sys/block/zram<id>/
|
|
|
|
disksize
|
|
|
|
num_reads
|
|
|
|
num_writes
|
2014-04-07 22:38:08 +00:00
|
|
|
failed_reads
|
|
|
|
failed_writes
|
2010-08-09 17:26:55 +00:00
|
|
|
invalid_io
|
|
|
|
notify_free
|
|
|
|
zero_pages
|
|
|
|
orig_data_size
|
|
|
|
compr_data_size
|
|
|
|
mem_used_total
|
2009-09-22 04:56:54 +00:00
|
|
|
|
2014-10-09 22:29:53 +00:00
|
|
|
8) Deactivate:
|
2010-06-01 08:01:26 +00:00
|
|
|
swapoff /dev/zram0
|
|
|
|
umount /dev/zram1
|
2009-09-22 04:56:54 +00:00
|
|
|
|
2014-10-09 22:29:53 +00:00
|
|
|
9) Reset:
|
2010-08-09 17:26:55 +00:00
|
|
|
Write any positive value to 'reset' sysfs node
|
|
|
|
echo 1 > /sys/block/zram0/reset
|
|
|
|
echo 1 > /sys/block/zram1/reset
|
|
|
|
|
2013-01-30 02:41:40 +00:00
|
|
|
This frees all the memory allocated for the given device and
|
|
|
|
resets the disksize to zero. You must set the disksize again
|
|
|
|
before reusing the device.
|
2009-09-22 04:56:54 +00:00
|
|
|
|
|
|
|
Nitin Gupta
|
|
|
|
ngupta@vflare.org
|