[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKEwX=PfRNLL_t5q8vfEKA_rxgFcAer=9EFwLWDo9kDsmroAGw@mail.gmail.com>
Date: Tue, 12 Dec 2023 15:33:47 -0800
From: Nhat Pham <nphamcs@...il.com>
To: Yosry Ahmed <yosryahmed@...gle.com>
Cc: Chengming Zhou <zhouchengming@...edance.com>,
Chris Li <chriscli@...gle.com>,
Vitaly Wool <vitaly.wool@...sulko.com>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Seth Jennings <sjenning@...hat.com>,
Dan Streetman <ddstreet@...e.org>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Matthew Wilcox <willy@...radead.org>
Subject: Re: [PATCH 0/7] mm/zswap: optimize the scalability of zswap rb-tree
On Tue, Dec 12, 2023 at 3:27 PM Yosry Ahmed <yosryahmed@...gle.com> wrote:
>
> Let's split the rbtree breakdown into a separate series. This series
> has irrelevant (and very nice) cleanups and optimizations, let's get
> them separately and defer the rbtree breakdown part until we get data
> about the xarray implementation. Perhaps the tree breakdown is not
> needed as much with an xarray, or at the very least the implementation
> would look different on top of an xarray.
Actually, kinda agree - I quite like the cleanup/optimization done
w.r.t dstmem reuse :)
Powered by blists - more mailing lists