From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: cmm@us.ibm.com
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/3] ext4 online defrag (ver 0.7)
Date: Mon, 10 Mar 2008 19:48:12 +0900 [thread overview]
Message-ID: <47D511EC.6000908@rs.jp.nec.com> (raw)
In-Reply-To: <1204934917.14884.70.camel@localhost.localdomain>
Hello Mingming,
Thank you for review. :-)
>> Next step:
>> Remove the limit of target file size (now 128MB) in -f mode.
>> * Past mail concerning -f mode.
>> http://marc.info/?l=linux-ext4&m=118239067704899&w=4
>>
>>
>
> The old version have many useful high level description, could you
> preserve that and add to the change logs in this updated series?
>
All right. I'll do so next time.
>> Dependency:
>> My patches depend on the multi-block allocation in ext4 patch queue.
>>
>>
> mballoc patch already in maintain so this dependency could be removed.
>
We have to set mballoc mount option for ext4 online defrag,
because it doesn't support single block allocation.
So I think ext4 online defrag depends on mballoc.
>> Summary of patches:
>> * These patches are applied on the top of
>> ext4 git tree(linux-2.6.25-rc3-git4).
>> http://repo.or.cz/r/ext4-patch-queue.git
>> And attached files are the updated patches.
>>
>>
>
> I assume the following three patches are diffs against current ext4
> patch queue
>
Exactly. Sorry for the confusion.
>> [PATCH 1/3]
>> - Interchange the data blocks of the target and
>> temporary files in an atomic manner.
>>
>> [PATCH 2/3]
>> - Change the name of functions.
>> ext4_ext_xxx -> ext4_defrag_xxx
>> - Some cleanups.
>>
>> [PATCH 3/3] ext4 online defrag command
>> - Change the error handling for ext4_iget().
>> - Usage is as follows:
>> o Put the multiple files closer together.
>> # e4defrag -r directory-name
>> o Defrag for free space fragmentation.
>> # e4defrag -f file-name
>> o Defrag for a single file.
>> # e4defrag file-name
>> o Defrag for all files on ext4.
>> # e4defrag device-name
>>
>> Review and comment are welcome.
>>
>>
>
> Attempted to do so...
>
> The updated patch series could not compile one-by-one, could you rework
> the series so that in the future we could able to bi-search the ext4
> patch queue?
OK.
I'll make my updated patches to compile one-by-one
then resend them to you.
> As a whole, I got compile warning when applied all the
> updated patches:(
>
Oops, I'll fix it. =-O
> review comments against the 4 updated kernel patches to follow.
>
I am confirming your review comments.
It will take time a little. :-)
Regards, Akira
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-03-10 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200803060001.AA00322@TNESG9526.rs.jp.nec.com>
2008-03-08 0:08 ` [RFC][PATCH 0/3] ext4 online defrag (ver 0.7) Mingming Cao
2008-03-08 1:20 ` [PATCH 2/5] ext4: online defrag-- Allocate new contiguous blocks with mballoc Mingming Cao
2008-04-11 7:32 ` Akira Fujita
2008-03-10 10:48 ` Akira Fujita [this message]
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=47D511EC.6000908@rs.jp.nec.com \
--to=a-fujita@rs.jp.nec.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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).