[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJD7tkZRnywCj4ha2hMcjQU7OjfR8DQ-Pi8K89NADxObCXvsMA@mail.gmail.com>
Date: Tue, 16 Jan 2024 12:22:03 -0800
From: Yosry Ahmed <yosryahmed@...gle.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Johannes Weiner <hannes@...xchg.org>,
Vlastimil Babka <vbabka@...e.cz>, 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:18 PM Matthew Wilcox <willy@...radead.org> wrote:
>
> 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?
+1. Both of these changes have been in Linus's tree for a while now.
Perhaps Andrew had this email prepared a while ago and never sent it,
and ended up fixing the problem himself.
Powered by blists - more mailing lists