From: "Theodore Ts'o" <tytso@mit.edu>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Transparent compression with ext4 - especially with zstd
Date: Mon, 20 Jan 2025 23:01:25 -0500 [thread overview]
Message-ID: <20250121040125.GC3761769@mit.edu> (raw)
In-Reply-To: <8cb4d855-6bd8-427f-ac8f-8cf7b91547fb@wiesinger.com>
On Sun, Jan 19, 2025 at 03:37:27PM +0100, Gerhard Wiesinger wrote:
>
> Are there any plans to include transparent compression with ext4 (especially
> with zstd)?
I'm not aware of anyone in the ext4 deveopment commuity working on
something like this. Fully transparent compression is challenging,
since supporting random writes into a compressed file is tricky.
There are solutions (for example, the Stac patent which resulted in
Microsoft to pay $120 million dollars), but even ignoring the
intellectual property issues, they tend to compromise the efficiency
of the compression.
More to the point, given how cheap byte storage tends to be (dollars
per IOPS tend to be far more of a constraint than dollars per GB),
it's unclear what the business case would be for any company to fund
development work in this area, when the cost of a slightly large HDD
or SSD is going to be far cheaper than the necessary software
engineering investrment needed, even for a hyperscaler cloud company
(and even there, it's unclear that transparent compression is really
needed).
What is the business and/or technical problem which you are trying to
solve?
Cheers,
- Ted
next prev parent reply other threads:[~2025-01-21 4:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 14:37 Transparent compression with ext4 - especially with zstd Gerhard Wiesinger
2025-01-21 4:01 ` Theodore Ts'o [this message]
2025-01-21 9:42 ` Artem Blagodarenko
2025-01-21 18:47 ` Gerhard Wiesinger
2025-01-21 19:33 ` Theodore Ts'o
2025-01-22 0:19 ` Kiselev, Oleg
2025-01-22 6:10 ` Gerhard Wiesinger
2025-01-22 7:29 ` Gerhard Wiesinger
2025-01-22 7:37 ` Christoph Hellwig
2025-01-22 13:19 ` Theodore Ts'o
2025-01-22 14:11 ` Christoph Hellwig
2025-01-21 21:26 ` Dave Chinner
2025-01-22 6:47 ` Gerhard Wiesinger
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=20250121040125.GC3761769@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@wiesinger.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