From: Sasha Levin <sashal@kernel.org>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: stable@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Chris Down <chris@chrisdown.name>, Nhat Pham <nphamcs@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vitaly Wool <vitaly.wool@konsulko.com>,
Christoph Hellwig <hch@lst.de>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Huacai Chen <chenhuacai@kernel.org>,
Miaohe Lin <linmiaohe@huawei.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
WANG Xuerui <kernel@xen0n.name>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.11.y] mm: z3fold: deprecate CONFIG_Z3FOLD
Date: Tue, 8 Oct 2024 02:04:23 -0400 [thread overview]
Message-ID: <ZwTLZ7rgSr58pqVq@sashalap> (raw)
In-Reply-To: <20241007192116.2529593-1-yosryahmed@google.com>
On Mon, Oct 07, 2024 at 07:21:16PM +0000, Yosry Ahmed wrote:
>The z3fold compressed pages allocator is rarely used, most users use
>zsmalloc. The only disadvantage of zsmalloc in comparison is the
>dependency on MMU, and zbud is a more common option for !MMU as it was the
>default zswap allocator for a long time.
Queued up, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-10-08 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 15:06 FAILED: patch "[PATCH] mm: z3fold: deprecate CONFIG_Z3FOLD" failed to apply to 6.11-stable tree gregkh
2024-10-07 19:21 ` [PATCH 6.11.y] mm: z3fold: deprecate CONFIG_Z3FOLD Yosry Ahmed
2024-10-08 6:04 ` Sasha Levin [this message]
2024-10-07 19:23 ` [PATCH 6.10.y] " Yosry Ahmed
2024-10-07 19:25 ` [PATCH 6.6.y] " Yosry Ahmed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZwTLZ7rgSr58pqVq@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=chris@chrisdown.name \
--cc=christophe.leroy@csgroup.eu \
--cc=hannes@cmpxchg.org \
--cc=hch@lst.de \
--cc=kernel@xen0n.name \
--cc=linmiaohe@huawei.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=nphamcs@gmail.com \
--cc=npiggin@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
--cc=vitaly.wool@konsulko.com \
--cc=yosryahmed@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox