Re: [PATCH v3 0/5] Implement writeback for zsmalloc

From: Johannes Weiner
Date: Tue Nov 08 2022 - 15:46:42 EST


On Tue, Nov 08, 2022 at 11:32:02AM -0800, Nhat Pham wrote:
> Changelog:
> v3:
> * Set pool->ops = NULL when pool->zpool_ops is null (patch 4).
> * Stop holding pool's lock when calling lock_zspage() (patch 5).
> (suggested by Sergey Senozhatsky)
> * Stop holding pool's lock when checking pool->ops and retries.
> (patch 5) (suggested by Sergey Senozhatsky)
> * Fix formatting issues (.shrink, extra spaces in casting removed).
> (patch 5) (suggested by Sergey Senozhatsky)
>
> v2:
> * Add missing CONFIG_ZPOOL ifdefs (patch 5)
> (detected by kernel test robot).
>
> Unlike other zswap's allocators such as zbud or z3fold, zsmalloc
> currently lacks the writeback mechanism. This means that when the zswap
> pool is full, it will simply reject further allocations, and the pages
> will be written directly to swap.
>
> This series of patches implements writeback for zsmalloc. When the zswap
> pool becomes full, zsmalloc will attempt to evict all the compressed
> objects in the least-recently used zspages.
>
> There are 5 patches in this series:

For the series:

Acked-by: Johannes Weiner <hannes@xxxxxxxxxxx>