From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Joey Pabalinas <joeypabalinas@gmail.com>,
Minchan Kim <minchan@kernel.org>
Subject: [PATCH v4 0/7] zram idle page writeback
Date: Mon, 3 Dec 2018 11:40:38 +0900 [thread overview]
Message-ID: <20181203024045.153534-1-minchan@kernel.org> (raw)
Inherently, swap device has many idle pages which are rare touched since
it was allocated. It is never problem if we use storage device as swap.
However, it's just waste for zram-swap.
This patchset supports zram idle page writeback feature.
* Admin can define what is idle page "no access since X time ago"
* Admin can define when zram should writeback them
* Admin can define when zram should stop writeback to prevent wearout
Detail is on each patch's description.
Below first two patches are -stable material so it could go first
separately with others in this series.
zram: fix lockdep warning of free block handling
zram: fix double free backing device
* from v3
- add more words in changelog - akpm
- clarification writeback limit - akpm
- fix 4k unit of bd_stat - akpm
- change writeback_limit interface - minchan
- add reviewed-by - sergey, joey
* from v2
- use strscpy instead of strlcpy - Joey Pabalinas
- remove irqlock for bitmap op - akpm
- don't use page as stat unit - akpm
* from v1
- add fix dobule free backing device - minchan
- change writeback/idle interface - minchan
- remove direct incompressible page writeback - sergey
Minchan Kim (7):
zram: fix lockdep warning of free block handling
zram: fix double free backing device
zram: refactoring flags and writeback stuff
zram: introduce ZRAM_IDLE flag
zram: support idle/huge page writeback
zram: add bd_stat statistics
zram: writeback throttle
Documentation/ABI/testing/sysfs-block-zram | 32 ++
Documentation/blockdev/zram.txt | 80 +++-
drivers/block/zram/Kconfig | 5 +-
drivers/block/zram/zram_drv.c | 502 +++++++++++++++------
drivers/block/zram/zram_drv.h | 19 +-
5 files changed, 476 insertions(+), 162 deletions(-)
--
2.20.0.rc1.387.gf8505762e3-goog
next reply other threads:[~2018-12-03 2:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 2:40 Minchan Kim [this message]
2018-12-03 2:40 ` [PATCH v4 1/7] zram: fix lockdep warning of free block handling Minchan Kim
2018-12-03 2:40 ` [PATCH v4 2/7] zram: fix double free backing device Minchan Kim
2018-12-03 2:40 ` [PATCH v4 3/7] zram: refactoring flags and writeback stuff Minchan Kim
2018-12-03 2:40 ` [PATCH v4 4/7] zram: introduce ZRAM_IDLE flag Minchan Kim
2018-12-03 2:40 ` [PATCH v4 5/7] zram: support idle/huge page writeback Minchan Kim
2018-12-03 2:40 ` [PATCH v4 6/7] zram: add bd_stat statistics Minchan Kim
2018-12-03 2:40 ` [PATCH v4 7/7] zram: writeback throttle Minchan Kim
2018-12-03 5:50 ` Sergey Senozhatsky
2018-12-03 6:02 ` Sergey Senozhatsky
2018-12-03 6:11 ` Sergey Senozhatsky
2018-12-04 2:08 ` [PATCH v4 0/7] zram idle page writeback Sergey Senozhatsky
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=20181203024045.153534-1-minchan@kernel.org \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=joeypabalinas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).