From: Eric Whitney <enwlinux@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, Eric Whitney <enwlinux@gmail.com>
Subject: [PATCH 0/6] improve cluster and block removal code
Date: Tue, 12 Sep 2023 22:11:42 -0400 [thread overview]
Message-ID: <20230913021148.1181646-1-enwlinux@gmail.com> (raw)
This patch series cleans up and rewrites parts of the code used to free
clusters or blocks when space is removed from a file. The intent is to
improve the readability, clarity, and efficiency of that code. These
changes do not fix any known bugs.
Eric Whitney (6):
ext4: consolidate code used to free clusters
ext4: rework partial cluster definition and related tracepoints
ext4: rework partial cluster handling to use lblk more consistently
ext4: consolidate partial cluster initialization
ext4: simplify and improve efficiency of cluster removal code
ext4: remove mballoc's NOFREE flags
fs/ext4/ext4.h | 4 +-
fs/ext4/ext4_extents.h | 19 +-
fs/ext4/extents.c | 371 ++++++++++++++++++------------------
fs/ext4/mballoc.c | 25 +--
include/trace/events/ext4.h | 123 ++++++++----
5 files changed, 287 insertions(+), 255 deletions(-)
--
2.30.2
next reply other threads:[~2023-09-13 2:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 2:11 Eric Whitney [this message]
2023-09-13 2:11 ` [PATCH 1/6] ext4: consolidate code used to free clusters Eric Whitney
2023-09-13 2:11 ` [PATCH 2/6] ext4: rework partial cluster definition and related tracepoints Eric Whitney
2023-09-13 2:11 ` [PATCH 3/6] ext4: rework partial cluster handling to use lblk more consistently Eric Whitney
2023-09-13 2:11 ` [PATCH 4/6] ext4: consolidate partial cluster initialization Eric Whitney
2023-09-13 2:11 ` [PATCH 5/6] ext4: simplify and improve efficiency of cluster removal code Eric Whitney
2023-09-13 2:11 ` [PATCH 6/6] ext4: remove mballoc's NOFREE flags Eric Whitney
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=20230913021148.1181646-1-enwlinux@gmail.com \
--to=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).