From: koraynilay <koray.fra@gmail.com>
To: clm@fb.com, dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org, koraynilay <koray.fra@gmail.com>
Subject: [PATCH 0/4] btrfs: add per-inode compression levels in xattrs
Date: Sat, 8 Aug 2026 04:34:55 +0200 [thread overview]
Message-ID: <20260808023459.1494928-1-koray.fra@gmail.com> (raw)
Add per-inode compression levels using
btrfs property set /path/to/file compression "algo:level", using the
same syntax as the compress mount option
If set on folders, all new children will inherit the setting, while
already existing children will be unaffected.
This patch series keeps a legacy small "bug": when setting
btrfs.compression, it keeps the mount option level, even if the algo is
different (!!), so with e.g. compress=zstd:15 and btrfs.compression=zlib
the data gets compressed at zlib:9 (because it still gets clamped at the
right range). This way the behaviour of chattr +c is also unchanged.
I also wanna thank Zygo for helping me by explaining stuff and for
noticing this "bug".
koraynilay (4):
btrfs: export btrfs_match_compress_type(), move it to compression.h
btrfs: also validate compression levels in
btrfs_compress_is_valid_type()
btrfs: add per-inode compression levels in xattrs
btrfs: support inheritance for per-inode compression levels
fs/btrfs/btrfs_inode.h | 1 +
fs/btrfs/compression.c | 28 ++++++++++++++++++---
fs/btrfs/compression.h | 3 ++-
fs/btrfs/inode.c | 14 +++++++++++
fs/btrfs/props.c | 57 +++++++++++++++++++++++++++++++++---------
fs/btrfs/super.c | 8 ------
6 files changed, 87 insertions(+), 24 deletions(-)
base-commit: a59f57e2aa127c5354168d2ec4bac920df1be4f4
--
2.55.0
next reply other threads:[~2026-08-08 2:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 2:34 koraynilay [this message]
2026-08-08 2:34 ` [PATCH 1/4] btrfs: export btrfs_match_compress_type(), move it to compression.h koraynilay
2026-08-08 2:34 ` [PATCH 2/4] btrfs: also validate compression levels in btrfs_compress_is_valid_type() koraynilay
2026-08-08 2:34 ` [PATCH 3/4] btrfs: add per-inode compression levels in xattrs koraynilay
2026-08-08 2:34 ` [PATCH 4/4] btrfs: support inheritance for per-inode compression levels koraynilay
2026-08-09 0:17 ` [PATCH 0/4] btrfs: add per-inode compression levels in xattrs Qu Wenruo
2026-08-09 0:35 ` koraynilay
2026-08-09 1:00 ` Qu Wenruo
2026-08-09 1:32 ` koraynilay
2026-08-09 23:17 ` Zygo Blaxell
2026-08-09 23:20 ` Qu Wenruo
2026-08-10 0:28 ` Zygo Blaxell
2026-08-10 0:51 ` Qu Wenruo
2026-08-10 0:57 ` Zygo Blaxell
2026-08-10 1:05 ` koraynilay
2026-08-10 1:54 ` Qu Wenruo
2026-08-10 1:57 ` koraynilay
2026-08-10 1:57 ` Qu Wenruo
2026-08-10 2:06 ` Zygo Blaxell
2026-08-10 2:11 ` Qu Wenruo
2026-08-10 22:41 ` koraynilay
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=20260808023459.1494928-1-koray.fra@gmail.com \
--to=koray.fra@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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