linux-kernel - Re: [PATCH 2/2] mm/zswap: use only one pool in zswap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKEwX=Pfi7XYdZN0O=RPJFcwrXLcho5SWQ62tc3v4+RafsZTkA@mail.gmail.com>
Date: Mon, 17 Jun 2024 10:01:48 -0700
From: Nhat Pham <nphamcs@...il.com>
To: Chengming Zhou <chengming.zhou@...ux.dev>
Cc: Minchan Kim <minchan@...nel.org>, Sergey Senozhatsky <senozhatsky@...omium.org>, 
	Andrew Morton <akpm@...ux-foundation.org>, Johannes Weiner <hannes@...xchg.org>, 
	Yosry Ahmed <yosryahmed@...gle.com>, Takero Funaki <flintglass@...il.com>, 
	Chengming Zhou <zhouchengming@...edance.com>, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] mm/zswap: use only one pool in zswap

On Mon, Jun 17, 2024 at 5:58 AM Chengming Zhou <chengming.zhou@...ux.dev> wrote:
>
> Zswap uses 32 pools to workaround the locking scalability problem in
> zsmalloc, which brings its own problems like memory waste and more
> memory fragmentation.
>
> Testing results show that we can have near performance with only one
> pool in zswap after changing zsmalloc to use per-size_class lock instead
> of pool spinlock.
>
> Testing kernel build (make bzImage -j32) on tmpfs with memory.max=1GB,
> and zswap shrinker enabled with 10GB swapfile on ext4.
>
>                                 real    user    sys
> 6.10.0-rc3                      138.18  1241.38 1452.73
> 6.10.0-rc3-onepool              149.45  1240.45 1844.69
> 6.10.0-rc3-onepool-perclass     138.23  1242.37 1469.71
>
> Signed-off-by: Chengming Zhou <chengming.zhou@...ux.dev>

Nice! I see minimal difference between one-pool-with-per-class lock
and current version, and the memory fragmentation should be reduced.

Anyway, I'll let the zsmalloc maintainers have the final say over
their side, but if this patch is picked up (and with the assumption
that the per-class lock is re-introduced), please feel free to
include:

Reviewed-by: Nhat Pham <nphamcs@...il.com>