From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Barry Song <baohua@kernel.org>,
akpm@linux-foundation.org, 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, Dongdong Zhang <zhangdongdong5@xiaomi.com>,
Suleiman Souhlal <suleiman@google.com>
Subject: Re: [RFC PATCH] zram: avoid preemption with CPU-based compression backends
Date: Fri, 14 Aug 2026 12:19:55 +0200 [thread overview]
Message-ID: <20260814101955.71AgFNAt@linutronix.de> (raw)
In-Reply-To: <anMPLgbrf7XMC7Qw@google.com>
On 2026-08-05 19:25:23 [+0900], Sergey Senozhatsky wrote:
> Hi Barry,
>
> On (26/08/05 15:50), Barry Song wrote:
> > BTW, I wonder if compression and decompression could use separate
> > mutexes. That way, a sleepable zs_malloc() in the compression path
> > would not block decompression, which is the more latency-sensitive
> > operation.
>
> quick and dirty patch. Just curious if this improves anything on your
> side.
>
> We also maybe can have more that num_online_cpus() stream, if we
> switch to idle streams list instead [1]
>
> [1] https://lore.kernel.org/lkml/20250130111105.2861324-3-senozhatsky@chromium.org/
After reading this thread, I got to say that this looks quite nice
compared to the other two ;)
Sebastian
next prev parent reply other threads:[~2026-08-14 10:20 UTC|newest]
Thread overview: 19+ 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 [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=20260814101955.71AgFNAt@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ryncsn@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=suleiman@google.com \
--cc=surenb@google.com \
--cc=yosry.ahmed@linux.dev \
--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