zram: support a page writeback
Subsystems (4)
Minchan Kim
maintainerPATCH 1/1 zram: support a page writeback
There is a demand to writeback specific pages on process to backing store instead of all idles pages in the system due to storage wear out concern and launching latency of apps which are most of time idle but critical for resume latency.
This patch extend writeback knob to support specific page writeback.
--- Documentation/admin-guide/blockdev/zram.rst | 5 +++++ drivers/block/zram/zram_drv.c | 14 ++++++++++---- 2 files changed, 15 insertions(+), 4 deletions(-)
Documentation/admin-guide/blockdev/zram.rst +5 -0
@@ -334,6 +334,11 @@ IOW, unless there is access request, those pages are still idle pages. With the command, zram writeback idle pages from memory to the storage. +If admin want to write a specific page in zram device to backing device, +they could write the page index into the interface. + + echo 1251 > /sys/block/zramX/writeback + If there are lots of write IO with flash device, potentially, it has flash wearout problem so that admin needs to design write limitation to guarantee storage health for entire product life.
drivers/block/zram/zram_drv.c +10 -4
@@ -618,6 +618,7 @@ static int read_from_bdev_async(struct zram *zram, struct bio_vec *bvec,return 1 ; } +#define PAGE_WRITEBACK 0#define HUGE_WRITEBACK 1#define IDLE_WRITEBACK 2
@@ -626,7 +627,7 @@ static ssize_t writeback_store(struct device *dev, {struct zram *zram =dev_to_zram (dev);unsigned long nr_pages = zram->disksize >>PAGE_SHIFT ; -unsigned long index; +unsigned long index =0 ;struct bio bio;struct bio_vec bio_vec;struct page *page;
@@ -638,8 +639,13 @@ static ssize_t writeback_store(struct device *dev, mode =IDLE_WRITEBACK ; else if (sysfs_streq(buf, "huge")) mode =HUGE_WRITEBACK ; - else - return -EINVAL; + else { + ret =kstrtol (buf,10 , &index); +if (ret || index >= nr_pages) +return -EINVAL ; + nr_pages =1 ; + mode =PAGE_WRITEBACK ; + }down_read (&zram->init_lock);if (!init_done (zram)) {
@@ -658,7 +664,7 @@ static ssize_t writeback_store(struct device *dev, goto release_init_lock; } -for (index =0 ; index < nr_pages; index++) { +while (nr_pages--) {struct bio_vec bvec; bvec.bv_page = page;
Signature · 1 line
2.28.0.1011.ga647a8990f-goog
Documentation/admin-guide/blockdev/zram.rst IOW, unless there is access request, those pages are still idle pages. · line 341
Quoted 8 lines · Minchan Kim
With the command, zram writeback idle pages from memory to the storage.
Documentation/admin-guide/blockdev/zram.rst +5
-0+If admin want to write a specific page in zram device to backing device, +they could write the page index into the interface. + + echo 1251 > /sys/block/zramX/writeback +
May be we can make it more explicit?
echo "page_index=123" > /sys/block/zramX/writeback
Just in case of future extensions. E.g. someone might want to have something like
echo "idle_nr=123" > /sys/block/zramX/writeback
which would write_back 123 idle pages max.
-ss
Minchan Kim
maintainerHi Sergey,
Quoted 14 lines · Sergey Senozhatsky
Documentation/admin-guide/blockdev/zram.rst IOW, unless there is access request, those pages are still idle pages. · line 341
Quoted 8 lines · Minchan Kim
With the command, zram writeback idle pages from memory to the storage.
Documentation/admin-guide/blockdev/zram.rst +5
-0+If admin want to write a specific page in zram device to backing device, +they could write the page index into the interface. + + echo 1251 > /sys/block/zramX/writeback +May be we can make it more explicit?
echo "page_index=123" >
/sys/block/zramX/writeback
Quoted 8 lines
Just in case of future extensions. E.g. someone might want to have something like
echo "idle_nr=123" > /sys/block/zramX/writebackwhich would
write_back123 idle pages max.-ss
Make sense. I will use echo "block_index" since page size could be changed later(e.g., some pages are 4K, some are THP).
I will revise it at next spin.
Thanks, Sergey!