From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Brian Geffon <bgeffon@google.com>,
Barry Song <baohua@kernel.org>, Bo Zhang <zhangbo0325@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Richard Chang <richardycc@google.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v7 00/15] zram: redesign zcomp and rework backends
Date: Fri, 30 Oct 2026 13:13:52 +0900 [thread overview]
Message-ID: <auQUjtWYOuhf_M8T@google.com> (raw)
In-Reply-To: <20261029200205.ee2a4788b8fdba4a75c2edd9@linux-foundation.org>
On (26/10/29 20:02), Andrew Morton wrote:
> On Sun, 25 Oct 2026 11:18:16 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
>
> > The series has a number of memory usage optimisations and fixes
> > that result in savings from double digits KB to triple digits
> > KB per-context/per-CPU, depending on backend and its configuration.
> > More details are in the corresponding commit messages.
>
> Thanks, I'll queue this.
>
> > drivers/block/zram/backend_842.c | 6 +-
> > drivers/block/zram/backend_deflate.c | 98 +++++----
> > drivers/block/zram/backend_lz4.c | 85 ++------
> > drivers/block/zram/backend_lz4hc.c | 105 ++++------
> > drivers/block/zram/backend_lzo.c | 6 +-
> > drivers/block/zram/backend_lzorle.c | 6 +-
> > drivers/block/zram/backend_zstd.c | 133 +++++++-----
> > drivers/block/zram/zcomp.c | 298 +++++++++++++++++++++++----
> > drivers/block/zram/zcomp.h | 53 ++++-
> > drivers/block/zram/zram_drv.c | 71 ++++---
> > 10 files changed, 546 insertions(+), 315 deletions(-)
>
> I've always put zram material into mm.git's mm-unstable/mm-stable branch.
> Because "ram", I guess.
>
> But it's a blockdev, so I'll henceforth carry it in mm.git's
> mm-nonmm-unstable/mm-nonmm-stable branches.
Thank you very much, sir.
next prev parent reply other threads:[~2026-10-30 4:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 2:18 [PATCH v7 00/15] zram: redesign zcomp and rework backends 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 [this message]
2026-10-31 2:58 ` zhangbo56
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=auQUjtWYOuhf_M8T@google.com \
--to=senozhatsky@chromium.org \
--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=zhangbo0325@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.