[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZabknuNmymSP0XgG@casper.infradead.org>
Date: Tue, 16 Jan 2024 20:18:38 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Johannes Weiner <hannes@...xchg.org>, Vlastimil Babka <vbabka@...e.cz>,
Yosry Ahmed <yosryahmed@...gle.com>,
Christoph Hellwig <hch@...radead.org>,
Nhat Pham <nphamcs@...il.com>,
Domenico Cerasuolo <cerasuolodomenico@...il.com>,
konrad.wilk@...cle.com, vitaly.wool@...sulko.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: kill frontswap
On Tue, Jan 16, 2024 at 12:09:44PM -0800, Andrew Morton wrote:
> On Mon, 17 Jul 2023 12:02:27 -0400 Johannes Weiner <hannes@...xchg.org> wrote:
>
> > The only user of frontswap is zswap, and has been for a long
> > time. Have swap call into zswap directly and remove the indirection.
>
> This falls afoul of "mm: zswap: multiple zpools support". Could we
> please have a version against mm-unstable or linux-next?
Did this email get caught in a timewarp? Or is it referring to
something that isn't commit 42c06a0e8ebe from six months ago?
Powered by blists - more mailing lists