[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOzc2pwzEVNDoXqXmG-Y+doBO=K9NY7=M5NGUJmohfjHcM5hyg@mail.gmail.com>
Date: Tue, 3 Sep 2024 10:35:09 -0700
From: Vishal Moola <vishal.moola@...il.com>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Matthew Wilcox <willy@...radead.org>, Yosry Ahmed <yosryahmed@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>, alexs@...nel.org,
Vitaly Wool <vitaly.wool@...sulko.com>, Miaohe Lin <linmiaohe@...wei.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, minchan@...nel.org,
david@...hat.com, 42.hyeyoo@...il.com, nphamcs@...il.com
Subject: Re: [PATCH v5 00/21] mm/zsmalloc: add zpdesc memory descriptor for zswap.zpool
On Mon, Sep 2, 2024 at 8:20 PM Sergey Senozhatsky
<senozhatsky@...omium.org> wrote:
>
> On (24/08/27 16:19), Vishal Moola wrote:
> >
> > Or should we aim to leave zsmalloc as it is currently implemented?
> >
>
> Is this really an option?
Yup. That would be similar to your initial suggestion: zpdescs would be a
wrapper around struct page and we "chain zpdesc-s together to form a zspage".
Although, we may as well aim for an improved implementation of zsmalloc (if at
all possible) since implementing the zpdesc wrapper requires us to modify a
good chunk of code anyways. That way zsmalloc gets direct wins for its users
on top of shrinking struct page as Matthew described before.
I believe you would be a better judge of whether or not any improvements
are feasible (and worth the effort).
Powered by blists - more mailing lists