From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Jianyue Wu <wujianyue000@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Li <chrisl@kernel.org>, Baoquan He <bhe@redhat.com>,
Nhat Pham <nphamcs@gmail.com>, Barry Song <baohua@kernel.org>,
Kairui Song <kasong@tencent.com>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Youngjun Park <youngjun.park@lge.com>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jens Axboe <axboe@kernel.dk>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Jan Kara <jack@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
Brian Geffon <bgeffon@google.com>
Subject: Re: [PATCH 0/3] mm/zram: route block swap I/O through swap_ops
Date: Wed, 17 Jun 2026 12:46:53 +0900 [thread overview]
Message-ID: <ajIYFtADxQDq8q1P@google.com> (raw)
In-Reply-To: <CAJxJ_jhK+zkpjhs3YsQ9RoasKYh+E0NweQci0sPAEY1ne5LmBA@mail.gmail.com>
Cc-ing Brian
On (26/06/17 11:38), Jianyue Wu wrote:
> > I fear this is going entirely in the wrong direction.
> OK. I was trying to build on your swap_iocb / swap_ops rework
> for the zram swap path, but I take your point that compressed swap can
> be handled more nicely.
>
> > Yes, we have to keep zram around as a legacy interface for now,
> > but the right place to deal with compressed swap is in the core.
> I agree compressed swap belongs in the core is better, so not only ram,
> but also the block layer can use it.
>
> Before I rework or drop the RFC, could you outline how you see that
> core-side model working? In particular:
> - How should a compressed backend like zram or future block device
> plug into swap_iocb / swap_ops?
> - What role do you expect zram to keep while the legacy block interface
> remains: current block swap only, or something else?
Those are fantastic questions, thank you for asking them.
Can we elaborate on zram being a "legacy interface"?
next prev parent reply other threads:[~2026-06-17 3:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 15:35 [PATCH 0/3] mm/zram: route block swap I/O through swap_ops Jianyue Wu
2026-06-14 15:35 ` [PATCH 1/3] mm/page_io: let block drivers register custom swap I/O ops Jianyue Wu
2026-06-15 1:50 ` YoungJun Park
2026-06-15 12:49 ` Jianyue Wu
2026-06-14 15:35 ` [PATCH 2/3] mm/zram: handle swap read/write via swap_ops Jianyue Wu
2026-06-15 6:39 ` YoungJun Park
2026-06-15 13:19 ` Jianyue Wu
2026-06-14 15:35 ` [PATCH 3/3] mm/swap: route slot free notifications through swap_ops Jianyue Wu
2026-06-15 9:14 ` [PATCH 0/3] mm/zram: route block swap I/O " Barry Song
2026-06-15 13:34 ` Jianyue Wu
2026-06-16 12:36 ` Christoph Hellwig
2026-06-17 3:38 ` Jianyue Wu
2026-06-17 3:46 ` Sergey Senozhatsky [this message]
2026-06-17 5:44 ` Jianyue Wu
2026-06-17 6:10 ` Sergey Senozhatsky
2026-06-17 6:19 ` Christoph Hellwig
2026-06-17 6:17 ` Christoph Hellwig
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=ajIYFtADxQDq8q1P@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=baohua@kernel.org \
--cc=bgeffon@google.com \
--cc=bhe@redhat.com \
--cc=chrisl@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=kasong@tencent.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=shikemeng@huaweicloud.com \
--cc=willy@infradead.org \
--cc=wujianyue000@gmail.com \
--cc=youngjun.park@lge.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