From: Sergio Abreu <dosergio@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: I have one idea to improve ext4 filesystem efficientcy
Date: Thu, 24 Jul 2025 08:56:49 -0300 [thread overview]
Message-ID: <de1f4f53-49b5-4d0e-a20d-f797b72b29be@gmail.com> (raw)
Hello
I am just in love with ext family file system!
I have studied it deeply and now I want to contribute with an idea that
could be used for next versions from ext4 and ahead
It's a simple thing that is fully compatible with current Ext4 version
and will improve space efficiency.
I don't really want to write code, just transfer my vision to an already
envolved and competent programmer that is working on ext4 development.
PS: I have contributed to other free open source projects. My name is
present in the Greasemonkey Mozilla extension (js expert) and as
TuxGuitar as translator.
Now I just wanted to share a tech insight that would improve ext4
efficiency even more.
Best Regards
Sergio Abreu - Brazilian developer since the year 2001
next reply other threads:[~2025-07-24 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 11:56 Sergio Abreu [this message]
2025-07-24 12:53 ` I have one idea to improve ext4 filesystem efficientcy Theodore Ts'o
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=de1f4f53-49b5-4d0e-a20d-f797b72b29be@gmail.com \
--to=dosergio@gmail.com \
--cc=linux-ext4@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