Nitin Gupta | 00ac9ba | 2010-06-01 13:31:26 +0530 | [diff] [blame] | 1 | zram: Compressed RAM based block devices |
| 2 | ---------------------------------------- |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 3 | |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 4 | * Introduction |
| 5 | |
Nitin Gupta | 9b9913d | 2010-08-09 22:56:55 +0530 | [diff] [blame] | 6 | The zram module creates RAM based block devices named /dev/zram<id> |
| 7 | (<id> = 0, 1, ...). Pages written to these disks are compressed and stored |
| 8 | in memory itself. These disks allow very fast I/O and compression provides |
| 9 | good amounts of memory savings. Some of the usecases include /tmp storage, |
| 10 | use as swap disks, various caches under /var and maybe many more :) |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 11 | |
Nitin Gupta | 9b9913d | 2010-08-09 22:56:55 +0530 | [diff] [blame] | 12 | Statistics for individual zram devices are exported through sysfs nodes at |
| 13 | /sys/block/zram<id>/ |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 14 | |
| 15 | * Usage |
| 16 | |
Nitin Gupta | 00ac9ba | 2010-06-01 13:31:26 +0530 | [diff] [blame] | 17 | Following shows a typical sequence of steps for using zram. |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 18 | |
Nitin Gupta | 9b9913d | 2010-08-09 22:56:55 +0530 | [diff] [blame] | 19 | 1) Load Module: |
Nitin Gupta | 00ac9ba | 2010-06-01 13:31:26 +0530 | [diff] [blame] | 20 | modprobe zram num_devices=4 |
Nitin Gupta | 9b9913d | 2010-08-09 22:56:55 +0530 | [diff] [blame] | 21 | This creates 4 devices: /dev/zram{0,1,2,3} |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 22 | (num_devices parameter is optional. Default: 1) |
| 23 | |
Sergey Senozhatsky | beca3ec | 2014-04-07 15:38:14 -0700 | [diff] [blame] | 24 | 2) Set max number of compression streams |
| 25 | Compression backend may use up to max_comp_streams compression streams, |
| 26 | thus allowing up to max_comp_streams concurrent compression operations. |
| 27 | By default, compression backend uses single compression stream. |
| 28 | |
| 29 | Examples: |
| 30 | #show max compression streams number |
| 31 | cat /sys/block/zram0/max_comp_streams |
| 32 | |
| 33 | #set max compression streams number to 3 |
| 34 | echo 3 > /sys/block/zram0/max_comp_streams |
| 35 | |
| 36 | Note: |
| 37 | In order to enable compression backend's multi stream support max_comp_streams |
| 38 | must be initially set to desired concurrency level before ZRAM device |
| 39 | initialisation. Once the device initialised as a single stream compression |
Minchan Kim | 60a726e | 2014-04-07 15:38:21 -0700 | [diff] [blame] | 40 | backend (max_comp_streams equals to 1), you will see error if you try to change |
| 41 | the value of max_comp_streams because single stream compression backend |
| 42 | implemented as a special case by lock overhead issue and does not support |
| 43 | dynamic max_comp_streams. Only multi stream backend supports dynamic |
| 44 | max_comp_streams adjustment. |
Sergey Senozhatsky | beca3ec | 2014-04-07 15:38:14 -0700 | [diff] [blame] | 45 | |
Sergey Senozhatsky | e46b8a0 | 2014-04-07 15:38:17 -0700 | [diff] [blame] | 46 | 3) Select compression algorithm |
| 47 | Using comp_algorithm device attribute one can see available and |
| 48 | currently selected (shown in square brackets) compression algortithms, |
| 49 | change selected compression algorithm (once the device is initialised |
| 50 | there is no way to change compression algorithm). |
| 51 | |
| 52 | Examples: |
| 53 | #show supported compression algorithms |
| 54 | cat /sys/block/zram0/comp_algorithm |
| 55 | lzo [lz4] |
| 56 | |
| 57 | #select lzo compression algorithm |
| 58 | echo lzo > /sys/block/zram0/comp_algorithm |
| 59 | |
| 60 | 4) Set Disksize |
Minchan Kim | 0231c40 | 2013-01-30 11:41:40 +0900 | [diff] [blame] | 61 | Set disk size by writing the value to sysfs node 'disksize'. |
| 62 | The value can be either in bytes or you can use mem suffixes. |
| 63 | Examples: |
| 64 | # Initialize /dev/zram0 with 50MB disksize |
| 65 | echo $((50*1024*1024)) > /sys/block/zram0/disksize |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 66 | |
Minchan Kim | 0231c40 | 2013-01-30 11:41:40 +0900 | [diff] [blame] | 67 | # Using mem suffixes |
| 68 | echo 256K > /sys/block/zram0/disksize |
| 69 | echo 512M > /sys/block/zram0/disksize |
| 70 | echo 1G > /sys/block/zram0/disksize |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 71 | |
Sergey Senozhatsky | e64cd51 | 2014-04-07 15:38:07 -0700 | [diff] [blame] | 72 | Note: |
| 73 | There is little point creating a zram of greater than twice the size of memory |
| 74 | since we expect a 2:1 compression ratio. Note that zram uses about 0.1% of the |
| 75 | size of the disk when not in use so a huge zram is wasteful. |
| 76 | |
Sergey Senozhatsky | e46b8a0 | 2014-04-07 15:38:17 -0700 | [diff] [blame] | 77 | 5) Activate: |
Nitin Gupta | 00ac9ba | 2010-06-01 13:31:26 +0530 | [diff] [blame] | 78 | mkswap /dev/zram0 |
| 79 | swapon /dev/zram0 |
| 80 | |
| 81 | mkfs.ext4 /dev/zram1 |
| 82 | mount /dev/zram1 /tmp |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 83 | |
Sergey Senozhatsky | e46b8a0 | 2014-04-07 15:38:17 -0700 | [diff] [blame] | 84 | 6) Stats: |
Nitin Gupta | 9b9913d | 2010-08-09 22:56:55 +0530 | [diff] [blame] | 85 | Per-device statistics are exported as various nodes under |
| 86 | /sys/block/zram<id>/ |
| 87 | disksize |
| 88 | num_reads |
| 89 | num_writes |
Sergey Senozhatsky | 8dd1d32 | 2014-04-07 15:38:08 -0700 | [diff] [blame] | 90 | failed_reads |
| 91 | failed_writes |
Nitin Gupta | 9b9913d | 2010-08-09 22:56:55 +0530 | [diff] [blame] | 92 | invalid_io |
| 93 | notify_free |
Nitin Gupta | 9b9913d | 2010-08-09 22:56:55 +0530 | [diff] [blame] | 94 | zero_pages |
| 95 | orig_data_size |
| 96 | compr_data_size |
| 97 | mem_used_total |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 98 | |
Sergey Senozhatsky | e46b8a0 | 2014-04-07 15:38:17 -0700 | [diff] [blame] | 99 | 7) Deactivate: |
Nitin Gupta | 00ac9ba | 2010-06-01 13:31:26 +0530 | [diff] [blame] | 100 | swapoff /dev/zram0 |
| 101 | umount /dev/zram1 |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 102 | |
Sergey Senozhatsky | e46b8a0 | 2014-04-07 15:38:17 -0700 | [diff] [blame] | 103 | 8) Reset: |
Nitin Gupta | 9b9913d | 2010-08-09 22:56:55 +0530 | [diff] [blame] | 104 | Write any positive value to 'reset' sysfs node |
| 105 | echo 1 > /sys/block/zram0/reset |
| 106 | echo 1 > /sys/block/zram1/reset |
| 107 | |
Minchan Kim | 0231c40 | 2013-01-30 11:41:40 +0900 | [diff] [blame] | 108 | This frees all the memory allocated for the given device and |
| 109 | resets the disksize to zero. You must set the disksize again |
| 110 | before reusing the device. |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 111 | |
Nitin Gupta | 47f9afb | 2009-09-22 10:26:54 +0530 | [diff] [blame] | 112 | Nitin Gupta |
| 113 | ngupta@vflare.org |