From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Bo Zhang <zhangbo0325@gmail.com>
Cc: senozhatsky@chromium.org, baohua@kernel.org,
akpm@linux-foundation.org, bigeasy@linutronix.de,
hdanton@sina.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, minchan@kernel.org, ryncsn@gmail.com,
yosry.ahmed@linux.dev, surenb@google.com, suleiman@google.com,
zhangdongdong5@xiaomi.com
Subject: Re: [RFC PATCH] zram: avoid preemption with CPU-based compression backends
Date: Tue, 13 Oct 2026 13:02:52 +0900 [thread overview]
Message-ID: <as2s0JflTS1wUUOl@google.com> (raw)
In-Reply-To: <20261012123328.1138059-1-zhangbo56@xiaomi.com>
Hi,
On (26/10/12 20:33), Bo Zhang wrote:
> On (26/08/05 19:25), Sergey Senozhatsky wrote:
> > quick and dirty patch. Just curious if this improves anything on your
> > side.
>
> Hi Sergey, Barry,
>
> I ran an A/B of the three approaches on a real Android device
> (MemTotal ~7.7GB, zram ~8GB). Same workload for all three: cycle 20
> memory-heavy apps through fg/bg to force swap-out/in, 8 rounds (~550s).
> The stream mutex is instrumented with a trylock-based counter; the
> measurement code is identical across all three builds, so the only
> difference is the patch.
Yeah, that patch was too quick and too dirty. We have significantly
reworked it in [1], specifically patches 9 and 10.
[1] https://lore.kernel.org/linux-kernel/20261013035201.2809924-1-senozhatsky@chromium.org
next prev parent reply other threads:[~2026-10-13 4:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 0:55 [RFC PATCH] zram: avoid preemption with CPU-based compression backends Barry Song (Xiaomi)
2026-08-05 1:27 ` Sergey Senozhatsky
2026-08-05 1:57 ` Barry Song
2026-08-05 2:09 ` Sergey Senozhatsky
2026-08-05 5:09 ` Barry Song
2026-08-05 5:21 ` Sergey Senozhatsky
2026-08-05 7:50 ` Barry Song
2026-08-05 8:46 ` Sergey Senozhatsky
2026-08-05 9:01 ` Sergey Senozhatsky
2026-08-05 10:07 ` Barry Song (Xiaomi)
2026-08-05 10:25 ` Sergey Senozhatsky
2026-08-05 10:34 ` Barry Song
2026-08-05 10:37 ` Sergey Senozhatsky
2026-08-14 10:19 ` Sebastian Andrzej Siewior
2026-10-12 12:33 ` Bo Zhang
2026-10-13 4:02 ` Sergey Senozhatsky [this message]
2026-08-05 2:19 ` Bo Zhang
2026-08-05 2:31 ` Barry Song
2026-08-05 7:30 ` Sergey Senozhatsky
2026-08-14 0:07 ` Barry Song
2026-08-14 4:29 ` Sergey Senozhatsky
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=as2s0JflTS1wUUOl@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ryncsn@gmail.com \
--cc=suleiman@google.com \
--cc=surenb@google.com \
--cc=yosry.ahmed@linux.dev \
--cc=zhangbo0325@gmail.com \
--cc=zhangdongdong5@xiaomi.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