mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: zhangbo56 <zhangbo0325@gmail.com>
To: senozhatsky@chromium.org
Cc: akpm@linux-foundation.org, baohua@kernel.org, bgeffon@google.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, minchan@kernel.org, richardycc@google.com,
	zhangbo0325@gmail.com, zhangbo56 <zhangbo56@xiaomi.com>
Subject: Re: [PATCH v7 00/15] zram: redesign zcomp and rework backends
Date: Sat, 31 Oct 2026 10:58:46 +0800	[thread overview]
Message-ID: <20261031025846.3774596-1-zhangbo56@xiaomi.com> (raw)
In-Reply-To: <20261025021839.1542805-1-senozhatsky@chromium.org>

I reported performance numbers earlier; this is a follow-up focused on
stability.

I ran an 8-hour stress test of this series using the following workload:
16 memcgs each looping a kernel build with tight memory limits to push
anon memory out to the zram swap (zstd), plus continuous CPU hotplug
(~113ms per cycle, 254k cycles). Repeated contained memcg OOM kills kept
the per-CPU streams constantly torn down and re-created under load.

Result: ran to completion, no issues.
  * dmesg clean - no BUG/Oops/stall/lockup/hung task/warning, no zram
    driver messages.
  * zram io_stat: failed_reads=0, failed_writes=0, invalid_io=0 across
    ~3.56 billion operations.
  * All CPUs back online cleanly.

A shorter lz4 (stateless) run was also clean.

Environment: 7.3.0-rc5-mmnew+, x86_64, PREEMPT, 28 CPUs, 8 GB RAM.

For the whole series:
Tested-by: zhangbo56 <zhangbo56@xiaomi.com>

Thanks,
Bo


      parent reply	other threads:[~2026-10-31  2:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25  2:18 Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 01/15] zram: prefix backends printk-s Sergey Senozhatsky
2026-10-25 10:05   ` Barry Song
2026-10-25  2:18 ` [PATCH v7 02/15] zram: remove debugfs entry on init failure Sergey Senozhatsky
2026-10-25 10:09   ` Barry Song
2026-10-25  2:18 ` [PATCH v7 03/15] zram: reset writeback state in zram_reset_device() Sergey Senozhatsky
2026-10-25 20:42   ` Barry Song
2026-10-25  2:18 ` [PATCH v7 04/15] zram: move mark_slot_accessed() under existing slot lock sections Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 05/15] zram: remove stale WARN_ON() from zram_read_page() Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 06/15] zram: zstd: do not allocate empty C/D-dictionaries Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 07/15] zram: lz4hc: pre-initialize dictionary stream in setup_params Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 08/15] zram: lz4: use LZ4_decompress_safe_usingDict() Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 09/15] zram: lz4hc: " Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 10/15] zram: zstd: do not use kvzalloc() for zstd allocations Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 11/15] zram: split zcomp into separate R/W streams Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 12/15] zram: introduce shared decompression streams Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 13/15] zram: allocate bounce buffer for spanning objects Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 14/15] zram: borrow idle decompression streams in exclusive mode Sergey Senozhatsky
2026-10-25  2:18 ` [PATCH v7 15/15] zram: use a singleton compression context for recompression Sergey Senozhatsky
2026-10-30  3:02 ` [PATCH v7 00/15] zram: redesign zcomp and rework backends Andrew Morton
2026-10-30  4:13   ` Sergey Senozhatsky
2026-10-31  2:58 ` zhangbo56 [this message]

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=20261031025846.3774596-1-zhangbo56@xiaomi.com \
    --to=zhangbo0325@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=bgeffon@google.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=richardycc@google.com \
    --cc=senozhatsky@chromium.org \
    --cc=zhangbo56@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
all inboxes | Powered by JetHome®