zram: update ac_time of written back slots#706
zram: update ac_time of written back slots#706blktests-ci[bot] wants to merge 1 commit intolinus-master_basefrom
Conversation
|
Upstream branch: 7aaa804 |
c781e1e to
255b4bf
Compare
|
Upstream branch: d0c3bcd |
de80631 to
a44d758
Compare
|
Upstream branch: d0c3bcd |
a44d758 to
a4d033f
Compare
255b4bf to
3236861
Compare
|
Upstream branch: 9147566 |
a4d033f to
31dbcdb
Compare
ecbdbb4 to
480b162
Compare
|
Upstream branch: 9147566 |
31dbcdb to
ab90ad2
Compare
a96fba7 to
0cd6ac2
Compare
|
Upstream branch: 9147566 |
ab90ad2 to
f2ca7c5
Compare
0cd6ac2 to
910d344
Compare
|
Upstream branch: d8a9a4b |
f2ca7c5 to
22a8ad6
Compare
910d344 to
ed862bc
Compare
|
Upstream branch: 7ca6d1c |
22a8ad6 to
6254587
Compare
ed862bc to
2d0c3d5
Compare
|
Upstream branch: 3aae938 |
6254587 to
4e9bf61
Compare
2d0c3d5 to
931d9b0
Compare
|
Upstream branch: 3036cd0 |
4e9bf61 to
13c6264
Compare
931d9b0 to
78a4682
Compare
|
Upstream branch: 9a9c8ce |
This makes it possible to tell how long each particular ZRAM_WB slot stays on the disk and, basically, to monitor writeback efficiency. Note that the patch factors out a small update_slot_ac_time() helper, which we call on writeback completion, instead of calling mark_slot_accessed(). The reasons being is that mark_slot_accessed() clears ZRAM_PP_SLOT flag ahead of time, while we want to keep that flag set as long as the slot is on the post-processing list (unless the slot is freed concurrently). Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org> Suggested-by: Suren Baghdasaryan <surenb@google.com> Suggested-by: Brian Geffon <bgeffon@google.com> Acked-by: Brian Geffon <bgeffon@google.com>
13c6264 to
b112c75
Compare
Pull request for series with
subject: zram: update ac_time of written back slots
version: 1
url: https://patchwork.kernel.org/project/linux-block/list/?series=1074971