[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221026200613.1031261-1-nphamcs@gmail.com>
Date: Wed, 26 Oct 2022 13:06:08 -0700
From: Nhat Pham <nphamcs@...il.com>
To: akpm@...ux-foundation.org
Cc: hannes@...xchg.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, minchan@...nel.org,
ngupta@...are.org, senozhatsky@...omium.org, sjenning@...hat.com,
ddstreet@...e.org, vitaly.wool@...sulko.com
Subject: [PATCH 0/5] Implement writeback for zsmalloc
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:
Johannes Weiner (1):
zswap: fix writeback lock ordering for zsmalloc
Nhat Pham (4):
zsmalloc: Consolidate zs_pool's migrate_lock and size_class's locks
zsmalloc: Add a LRU to zs_pool to keep track of zspages in LRU order
zsmalloc: Add ops fields to zs_pool to store evict handlers
zsmalloc: Implement writeback mechanism for zsmalloc
mm/zsmalloc.c | 336 ++++++++++++++++++++++++++++++++++++++++----------
mm/zswap.c | 37 +++---
2 files changed, 293 insertions(+), 80 deletions(-)
--
2.30.2
Powered by blists - more mailing lists