Skip to content

zram memory tracking

Minchan Kim lkml 5 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v5 Latest4 patches 7 repliesIn review
  2. v44 patches 4 repliesSuperseded
  3. v34 patches 6 repliesSuperseded
Earlier versions · 2
VersionPostedPatchesRepliesStatus
v24 patches3 repliesSuperseded
v12 patches9 repliesSuperseded

Patches in v5 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4zram: correct flag name of ZRAM_ACCESSdrivers/block/zram/zram_drv.c drivers/block/zram/zram_drv.h+13 -130 replies
2/4zram: mark incompressible page as ZRAM_HUGEDocumentation/blockdev/zram.txt drivers/block/zram/zram_drv.c drivers/block/zram/zram_drv.h+17 -30 replies
3/4zram: record accessed seconddrivers/block/zram/zram_drv.c drivers/block/zram/zram_drv.h+17 -00 replies
4/4zram: introduce zram memory trackingDocumentation/blockdev/zram.txt drivers/block/zram/Kconfig drivers/block/zram/zram_drv.c +1 more+170 -137 replies

Reviews trailers per patch

All 4 patches have a Reviewed-by or Acked-by.

PatchGreg Kroah-HartmanSergey Senozhatsky
1/4R-b
2/4R-b
3/4R-b
4/4A-b A-b R-b R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v5 thread

Cover letter [PATCH v5 0/4] zram memory tracking

zRam as swap is useful for small memory device. However, swap means those pages on zram are mostly cold pages due to VM's LRU algorithm. Especially, once init data for application are touched for launching, they tend to be not accessed any more and finally swapped out. zRAM can store such cold pages as compressed form but it's pointless to keep in memory. As well, it's pointless to store incompressible pages to zram so better idea is app developers manages them directly like free or mlock rather than remaining them on heap.

This patch provides a debugfs /sys/kernel/debug/zram/zram0/block_state to represent each block's state so admin can investigate what memory is cold|incompressible|same page with using pagemap once the pages are swapped out.

The output is as follows,

      300    75.033841 .wh
      301    63.806904 s..
      302    63.806919 ..h

First column is zram's block index and 3rh one represents symbol (s: same page w: written page to backing store h: huge page) of the block state. Second column represents usec time unit of the block was last accessed. So above example means the 300th block is accessed at 75.033851 second and it was huge so it was written to the backing store.

* from v4:
* Fix typos - Randy
* Add reviewed-by from Sergey

* from v3:
* use depends on selecting DEBUG_FS - Greg KH
* Add acked-by from Greg
* Fix null ptr access at module unload - Sergey
* warning fix from copy_to_user - Sergey

* From v2:
* debugfs and Kconfig cleanup - Greg KH
* Remove unnecesarry buffer - Sergey
* Change timestamp from sec to usec

* From v1:
* Do not propagate error number for debugfs fail - Greg KH
* Add writeback and hugepage information - Serge

Minchan Kim (4):
zram: correct flag name of ZRAM_ACCESS
zram: mark incompressible page as ZRAM_HUGE
zram: record accessed second
zram: introduce zram memory tracking

 Documentation/blockdev/zram.txt |  25 +++++
 drivers/block/zram/Kconfig      |  14 ++-
 drivers/block/zram/zram_drv.c   | 173 +++++++++++++++++++++++++++++---
 drivers/block/zram/zram_drv.h   |  14 ++-
 4 files changed, 207 insertions(+), 19 deletions(-)
Signature · 1 line
2.17.0.484.g0c8726318c-goog