From: Theodore Tso <tytso@mit.edu>
To: Akira Fujita <a-fujita@rs.jp.nec.com>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/12]ext4: online defrag (ver 0.95)
Date: Sun, 28 Sep 2008 19:46:40 -0400 [thread overview]
Message-ID: <20080928234640.GF8711@mit.edu> (raw)
In-Reply-To: <20080927144924.GA11669@mit.edu>
I've added online defrag version 0.95 into the ext4 patch queue.
Because of the recent patch I've added to remove the old legacy block
allocator patches 7 through 11 would no longer apply, and so they are
commented out in the patch queue. In some cases, the patches are ones
that would go away soon anyway. In the case of EXT4_IOC_RESERVE_BLOCK
ioctl, it was non-functional in the common case where mballoc was in
use, since mballoc never used any of the legacy block reservation
code; so any user space that depended on EXT4_IOC_RESERVE_BLOCK ioctl
couldn't possibly have worked.
If there are needed functions that were removed from mballoc.c that
really are necessary, we can certainly look at adding them back ---
but I would want to check to see if there is similar code in mballoc
that we can use instead. One of my concerns is that there is been
duplicated code in balloc.c, mballoc.c, extents.c, and defrag.c and
one of the reasons why I wanted to pull out the legacy block
allocation code was to eliminate some of the duplicated code, and to
hopefully expose more of this duplicated code.
In the end it should make all the ext4 code base and the defrag code
more easy to understand and much more robust.
Regards,
- Ted
next prev parent reply other threads:[~2008-09-28 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 7:26 [RFC][PATCH 0/12]ext4: online defrag (ver 0.95) Akira Fujita
2008-09-27 14:49 ` Theodore Tso
2008-09-28 23:46 ` Theodore Tso [this message]
2008-10-01 0:40 ` Andreas Dilger
2008-10-01 18:45 ` Christoph Hellwig
2008-10-01 21:20 ` Theodore Tso
2008-10-02 8:10 ` Andreas Dilger
2008-10-02 8:26 ` Christoph Hellwig
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=20080928234640.GF8711@mit.edu \
--to=tytso@mit.edu \
--cc=a-fujita@rs.jp.nec.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).