Cap the zram hit rate at 100 % #2
Loading…
Reference in a new issue
No description provided.
Delete branch "compswap-zram"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The zram block counter also counts reads that are not swap-ins (udev/blkid
probing, mkswap, swapon header), which could push the hit rate above 100 %
when there is little swap-in. Cap the zram reads at pswpin, and do not count
pages read back from the writeback backing device as served from RAM.