2010-08-09 22:56:56 +05:30
|
|
|
What: /sys/block/zram<id>/disksize
|
|
|
|
|
Date: August 2010
|
|
|
|
|
Contact: Nitin Gupta <ngupta@vflare.org>
|
|
|
|
|
Description:
|
|
|
|
|
The disksize file is read-write and specifies the disk size
|
|
|
|
|
which represents the limit on the *uncompressed* worth of data
|
|
|
|
|
that can be stored in this disk.
|
2013-08-26 14:55:44 -07:00
|
|
|
Unit: bytes
|
2010-08-09 22:56:56 +05:30
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/initstate
|
|
|
|
|
Date: August 2010
|
|
|
|
|
Contact: Nitin Gupta <ngupta@vflare.org>
|
|
|
|
|
Description:
|
2013-08-26 14:55:44 -07:00
|
|
|
The initstate file is read-only and shows the initialization
|
2010-08-09 22:56:56 +05:30
|
|
|
state of the device.
|
|
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/reset
|
|
|
|
|
Date: August 2010
|
|
|
|
|
Contact: Nitin Gupta <ngupta@vflare.org>
|
|
|
|
|
Description:
|
2013-08-26 14:55:44 -07:00
|
|
|
The reset file is write-only and allows resetting the
|
|
|
|
|
device. The reset operation frees all the memory associated
|
2010-08-09 22:56:56 +05:30
|
|
|
with this device.
|
|
|
|
|
|
2014-04-07 15:38:17 -07:00
|
|
|
What: /sys/block/zram<id>/comp_algorithm
|
|
|
|
|
Date: February 2014
|
|
|
|
|
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
|
|
|
|
|
Description:
|
|
|
|
|
The comp_algorithm file is read-write and lets to show
|
|
|
|
|
available and selected compression algorithms, change
|
|
|
|
|
compression algorithm selection.
|
|
|
|
|
|
2014-10-09 15:29:55 -07:00
|
|
|
What: /sys/block/zram<id>/mem_used_max
|
|
|
|
|
Date: August 2014
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
2017-02-22 15:46:45 -08:00
|
|
|
The mem_used_max file is write-only and is used to reset
|
|
|
|
|
the counter of maximum memory zram have consumed to store
|
|
|
|
|
compressed data. For resetting the value, you should write
|
|
|
|
|
"0". Otherwise, you could see -EINVAL.
|
2014-10-09 15:29:55 -07:00
|
|
|
Unit: bytes
|
|
|
|
|
|
2014-10-09 15:29:53 -07:00
|
|
|
What: /sys/block/zram<id>/mem_limit
|
|
|
|
|
Date: August 2014
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
2017-02-22 15:46:45 -08:00
|
|
|
The mem_limit file is write-only and specifies the maximum
|
|
|
|
|
amount of memory ZRAM can use to store the compressed data.
|
|
|
|
|
The limit could be changed in run time and "0" means disable
|
|
|
|
|
the limit. No limit is the initial state. Unit: bytes
|
2015-04-15 16:15:36 -07:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/compact
|
|
|
|
|
Date: August 2015
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
|
|
|
|
The compact file is write-only and trigger compaction for
|
|
|
|
|
allocator zrm uses. The allocator moves some objects so that
|
|
|
|
|
it could free fragment space.
|
2015-04-15 16:16:03 -07:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/io_stat
|
|
|
|
|
Date: August 2015
|
|
|
|
|
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
|
|
|
|
|
Description:
|
|
|
|
|
The io_stat file is read-only and accumulates device's I/O
|
|
|
|
|
statistics not accounted by block layer. For example,
|
|
|
|
|
failed_reads, failed_writes, etc. File format is similar to
|
|
|
|
|
block layer statistics file format.
|
2015-04-15 16:16:06 -07:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/mm_stat
|
|
|
|
|
Date: August 2015
|
|
|
|
|
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
|
|
|
|
|
Description:
|
|
|
|
|
The mm_stat file is read-only and represents device's mm
|
|
|
|
|
statistics (orig_data_size, compr_data_size, etc.) in a format
|
|
|
|
|
similar to block layer statistics file format.
|
2016-05-20 17:00:02 -07:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/debug_stat
|
|
|
|
|
Date: July 2016
|
|
|
|
|
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
|
|
|
|
|
Description:
|
|
|
|
|
The debug_stat file is read-only and represents various
|
|
|
|
|
device's debugging info useful for kernel developers. Its
|
|
|
|
|
format is not documented intentionally and may change
|
|
|
|
|
anytime without any notice.
|
2017-09-06 16:20:10 -07:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/backing_dev
|
|
|
|
|
Date: June 2017
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
|
|
|
|
The backing_dev file is read-write and set up backing
|
|
|
|
|
device for zram to write incompressible pages.
|
|
|
|
|
For using, user should enable CONFIG_ZRAM_WRITEBACK.
|
2018-12-28 00:36:44 -08:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/idle
|
|
|
|
|
Date: November 2018
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
|
|
|
|
idle file is write-only and mark zram slot as idle.
|
|
|
|
|
If system has mounted debugfs, user can see which slots
|
|
|
|
|
are idle via /sys/kernel/debug/zram/zram<id>/block_state
|
zram: support idle/huge page writeback
Add a new feature "zram idle/huge page writeback". In the zram-swap use
case, zram usually has many idle/huge swap pages. It's pointless to keep
them in memory (ie, zram).
To solve this problem, this feature introduces idle/huge page writeback to
the backing device so the goal is to save more memory space on embedded
systems.
Normal sequence to use idle/huge page writeback feature is as follows,
while (1) {
# mark allocated zram slot to idle
echo all > /sys/block/zram0/idle
# leave system working for several hours
# Unless there is no access for some blocks on zram,
# they are still IDLE marked pages.
echo "idle" > /sys/block/zram0/writeback
or/and
echo "huge" > /sys/block/zram0/writeback
# write the IDLE or/and huge marked slot into backing device
# and free the memory.
}
Per the discussion at
https://lore.kernel.org/lkml/20181122065926.GG3441@jagdpanzerIV/T/#u,
This patch removes direct incommpressibe page writeback feature
(d2afd25114f4 ("zram: write incompressible pages to backing device")).
Below concerns from Sergey:
== &< ==
"IDLE writeback" is superior to "incompressible writeback".
"incompressible writeback" is completely unpredictable and uncontrollable;
it depens on data patterns and compression algorithms. While "IDLE
writeback" is predictable.
I even suspect, that, *ideally*, we can remove "incompressible writeback".
"IDLE pages" is a super set which also includes "incompressible" pages.
So, technically, we still can do "incompressible writeback" from "IDLE
writeback" path; but a much more reasonable one, based on a page idling
period.
I understand that you want to keep "direct incompressible writeback"
around. ZRAM is especially popular on devices which do suffer from flash
wearout, so I can see "incompressible writeback" path becoming a dead
code, long term.
== &< ==
Below concerns from Minchan:
== &< ==
My concern is if we enable CONFIG_ZRAM_WRITEBACK in this implementation,
both hugepage/idlepage writeck will turn on. However someuser want to
enable only idlepage writeback so we need to introduce turn on/off knob
for hugepage or new CONFIG_ZRAM_IDLEPAGE_WRITEBACK for those usecase. I
don't want to make it complicated *if possible*.
Long term, I imagine we need to make VM aware of new swap hierarchy a
little bit different with as-is. For example, first high priority swap
can return -EIO or -ENOCOMP, swap try to fallback to next lower priority
swap device. With that, hugepage writeback will work tranparently.
So we could regard it as regression because incompressible pages doesn't
go to backing storage automatically. Instead, user should do it via "echo
huge" > /sys/block/zram/writeback" manually.
== &< ==
Link: http://lkml.kernel.org/r/20181127055429.251614-6-minchan@kernel.org
Signed-off-by: Minchan Kim <minchan@kernel.org>
Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com>
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-12-28 00:36:47 -08:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/writeback
|
|
|
|
|
Date: November 2018
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
|
|
|
|
The writeback file is write-only and trigger idle and/or
|
|
|
|
|
huge page writeback to backing device.
|
2018-12-28 00:36:51 -08:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/bd_stat
|
|
|
|
|
Date: November 2018
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
|
|
|
|
The bd_stat file is read-only and represents backing device's
|
|
|
|
|
statistics (bd_count, bd_reads, bd_writes) in a format
|
|
|
|
|
similar to block layer statistics file format.
|
2018-12-28 00:36:54 -08:00
|
|
|
|
2019-01-08 15:22:53 -08:00
|
|
|
What: /sys/block/zram<id>/writeback_limit_enable
|
|
|
|
|
Date: November 2018
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
|
|
|
|
The writeback_limit_enable file is read-write and specifies
|
|
|
|
|
eanbe of writeback_limit feature. "1" means eable the feature.
|
|
|
|
|
No limit "0" is the initial state.
|
|
|
|
|
|
2018-12-28 00:36:54 -08:00
|
|
|
What: /sys/block/zram<id>/writeback_limit
|
|
|
|
|
Date: November 2018
|
|
|
|
|
Contact: Minchan Kim <minchan@kernel.org>
|
|
|
|
|
Description:
|
|
|
|
|
The writeback_limit file is read-write and specifies the maximum
|
|
|
|
|
amount of writeback ZRAM can do. The limit could be changed
|
2019-01-08 15:22:53 -08:00
|
|
|
in run time.
|
2022-11-15 11:03:14 +09:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/recomp_algorithm
|
|
|
|
|
Date: November 2022
|
|
|
|
|
Contact: Sergey Senozhatsky <senozhatsky@chromium.org>
|
|
|
|
|
Description:
|
|
|
|
|
The recomp_algorithm file is read-write and allows to set
|
|
|
|
|
or show secondary compression algorithms.
|
|
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/recompress
|
|
|
|
|
Date: November 2022
|
|
|
|
|
Contact: Sergey Senozhatsky <senozhatsky@chromium.org>
|
|
|
|
|
Description:
|
|
|
|
|
The recompress file is write-only and triggers re-compression
|
|
|
|
|
with secondary compression algorithms.
|
2024-09-02 19:56:03 +09:00
|
|
|
|
|
|
|
|
What: /sys/block/zram<id>/algorithm_params
|
|
|
|
|
Date: August 2024
|
|
|
|
|
Contact: Sergey Senozhatsky <senozhatsky@chromium.org>
|
|
|
|
|
Description:
|
|
|
|
|
The algorithm_params file is write-only and is used to setup
|
|
|
|
|
compression algorithm parameters.
|