[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJD7tkaYnHvQmq=6OfHP-k7Bgq650xYJz=o7XzAg7ArGNtxQxQ@mail.gmail.com>
Date: Mon, 24 Jun 2024 04:39:07 -0700
From: Yosry Ahmed <yosryahmed@...gle.com>
To: Yu Zhao <yuzhao@...gle.com>
Cc: Chengming Zhou <chengming.zhou@...ux.dev>, Minchan Kim <minchan@...nel.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>, Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>, Nhat Pham <nphamcs@...il.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 1:20 PM Yu Zhao <yuzhao@...gle.com> wrote:
>
> On Mon, Jun 17, 2024 at 2:16 PM Yu Zhao <yuzhao@...gle.com> wrote:
> >
> > On Mon, Jun 17, 2024 at 6:58 AM Chengming Zhou <chengming.zhou@...ux.dev> wrote:
> > >
> > > Zswap uses 32 pools to workaround the locking scalability problem in
> > > zsmalloc,
> >
> > Note that zpool can have other backends (zbud, z3fold), and the
> > original patch was developed (even before zswap could use zsmalloc) to
> > make sure it works for all the backend.
> >
> > This patch only makes sense now only because zsmalloc became a lot
> > more popular than other backends (even though some distros still
> > default to zbud).
>
> And this might also have answered Yosry's question about the
> "historical context" here [1].
>
> [1] https://lore.kernel.org/CAJD7tkbO+ZLdhs-9BpthztZX32i8C4=QEnoiXGS7bM399nqwzg@mail.gmail.com/
It does, thanks.
Powered by blists - more mailing lists