From: Kazuya Mio <k-mio@sx.jp.nec.com>
To: ext4 <linux-ext4@vger.kernel.org>, Theodore Tso <tytso@mit.edu>
Subject: [PATCH 00/11 RESEND] e4defrag: fragmentation score rework and cleanups
Date: Wed, 15 Jun 2011 15:33:03 +0900 [thread overview]
Message-ID: <4DF8521F.2090400@sx.jp.nec.com> (raw)
Hi,
This patch set adds the new function get_fragment_score() to libe2p, that
calculates the fragmentation score. Fragmentation score shows how badly
fragmented the file might be. filefrag uses it to make a user understand
the status of the file fragmentation easily. And e4defrag also uses it
to determine smarter whether to call EXT4_IOC_MOVE_EXT ioctl. This improvement
is based on the following Ted's idea.
http://marc.info/?l=linux-ext4&m=129324612305011&w=4
In addition, the 6th to the last is bugfix or cleanup patch.
This patch set is for e2fsprogs git tree. (commit:2d34a25f81)
Kazuya Mio (11):
libe2p: Add new function get_fragment_score()
filefrag: Output fragmentation score
e4defrag: Remove -c option which check the file fragments
e4defrag: Remove old fragmentation score calculation code
e4defrag: Use get_fragment_score() for decision of whether to defrag
e4defrag: Allow user who has read+write permission to defrag
e4defrag: Fix memory leak in file_defrag()
e4defrag: Use blk64_t instead of ext4_fsblk_t
e4defrag: Use EXT2_SUPER_MAGIC instead of EXT4_SUPER_MAGIC
e4defrag: Fix error messages more clearly
e4defrag: Remove unnecessary code
lib/e2p/Makefile.in | 6
lib/e2p/e2p.h | 2
lib/e2p/fragment_score.c | 142 +++++++
misc/Makefile.in | 8
misc/e4defrag.8.in | 30 -
misc/e4defrag.c | 889 +++++------------------------------------------
misc/filefrag.c | 28 +
7 files changed, 288 insertions(+), 817 deletions(-)
Regards,
Kazuya Mio
next reply other threads:[~2011-06-15 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 6:33 Kazuya Mio [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-15 20:31 [PATCH 00/11 RESEND] e4defrag: fragmentation score rework and cleanups Tomasz Chmielewski
2011-06-16 5:10 ` Kazuya Mio
2011-06-16 8:18 ` Tomasz Chmielewski
2011-06-17 5:13 ` Kazuya Mio
2011-06-17 13:08 ` Greg Freemyer
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=4DF8521F.2090400@sx.jp.nec.com \
--to=k-mio@sx.jp.nec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.