From: Andrew Morton <akpm@linux-foundation.org>
To: Wenchao Hao <haowenchao22@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Nhat Pham <nphamcs@gmail.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Barry Song <baohua@kernel.org>,
Wenchao Hao <haowenchao@xiaomi.com>
Subject: Re: [PATCH v3 0/4] mm/zsmalloc: reduce lock contention in zs_free()
Date: Fri, 5 Jun 2026 18:19:31 -0700 [thread overview]
Message-ID: <20260605181931.d6fed8b62c8d91b27d151e71@linux-foundation.org> (raw)
In-Reply-To: <20260605084242.1549811-1-haowenchao22@gmail.com>
On Fri, 5 Jun 2026 16:42:38 +0800 Wenchao Hao <haowenchao22@gmail.com> wrote:
> This series reduces lock contention in zs_free(), which dominates the
> unmap path under memory pressure on Android (LMK kills) and on x86
> servers running zswap-heavy workloads.
Thanks. It's late in the cycle so I'd prefer to merge this after 7.2-rc1, please.
AI review said a few things:
https://sashiko.dev/#/patchset/20260605084242.1549811-1-haowenchao22@gmail.com
next prev parent reply other threads:[~2026-06-06 1:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 8:42 Wenchao Hao
2026-06-05 8:42 ` [PATCH v3 1/4] mm/zsmalloc: encode class index in obj value for lockless class lookup Wenchao Hao
2026-06-05 8:42 ` [PATCH v3 2/4] mm/zsmalloc: drop pool->lock from zs_free on 64-bit systems Wenchao Hao
2026-06-05 8:42 ` [PATCH v3 3/4] mm/zsmalloc: drop class lock before freeing zspage Wenchao Hao
2026-06-05 8:42 ` [PATCH v3 4/4] mm/zsmalloc: document free_zspage helper variants Wenchao Hao
2026-06-05 16:34 ` Nhat Pham
2026-06-09 11:31 ` Wenchao Hao
2026-06-06 1:19 ` Andrew Morton [this message]
2026-06-09 11:27 ` [PATCH v3 0/4] mm/zsmalloc: reduce lock contention in zs_free() Wenchao Hao
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=20260605181931.d6fed8b62c8d91b27d151e71@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=haowenchao22@gmail.com \
--cc=haowenchao@xiaomi.com \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=senozhatsky@chromium.org \
/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
all inboxes | Powered by JetHome®