From: Askar Safin <safinaskar@gmail.com>
To: bhe@redhat.com
Cc: 21cnbao@gmail.com, chrisl@kernel.org, kasong@tencent.com,
linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
youngjun.park@lge.com, Nhat Pham <nphamcs@gmail.com>,
Kairui Song <ryncsn@gmail.com>
Subject: Re: [LSF/MM/BPF TOPIC] swap_ops and plugable swap back end
Date: Tue, 24 Mar 2026 15:46:45 +0300 [thread overview]
Message-ID: <20260324124645.3944104-1-safinaskar@gmail.com> (raw)
In-Reply-To: <aZiFvzlBJiYBUDre@MiWiFi-R3L-srv>
Baoquan He <bhe@redhat.com>:
> How to handle storing compressed data. e.g. data from zram directly
> write to the swap backend without uncompressing.
This is already implemented here: https://lore.kernel.org/all/20251201094754.4149975-1-senozhatsky@chromium.org/ .
The patch is already in mainline.
--
Askar Safin
prev parent reply other threads:[~2026-03-24 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 16:03 [LSF/MM/BPF TOPIC] swap_ops and plugable swap back end Baoquan He
2026-03-24 12:46 ` Askar Safin [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=20260324124645.3944104-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=21cnbao@gmail.com \
--cc=bhe@redhat.com \
--cc=chrisl@kernel.org \
--cc=kasong@tencent.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=nphamcs@gmail.com \
--cc=ryncsn@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