[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080928234640.GF8711@mit.edu>
Date: Sun, 28 Sep 2008 19:46:40 -0400
From: Theodore Tso <tytso@....edu>
To: Akira Fujita <a-fujita@...jp.nec.com>
Cc: linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [RFC][PATCH 0/12]ext4: online defrag (ver 0.95)
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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists