All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: cmm@us.ibm.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC][PATCH 0/8] ext4 online defrag (ver 0.8)
Date: Mon, 14 Apr 2008 13:14:05 +0900	[thread overview]
Message-ID: <4802DA0D.4060502@rs.jp.nec.com> (raw)
In-Reply-To: <1207945113.3639.5.camel@localhost.localdomain>

Hello,

Mingming Cao wrote:
>> Summary of patches:
>> * These patches are replaced with ext4 online defrag patches
>>   which are already in the ext4 git tree (linux-2.6.26-rc8).
>>
>> [PATCH 1/8]  Exchange the blocks between two inodes
>> - Exchange the data blocks between the temporary inode and
>>   the original inode.
>>
>> [PATCH 2/8] Read and write file data with memory page
>> - Read the file data from the old blocks to the page and
>>   write the file data on the page into the new blocks.
>>
>> [PATCH 3/8] Allocate new contiguous blocks with mballoc
>> - Search contiguous free blocks with mutil-block allocation
>>   and allocate them for the temporary inode.
>>
>> [PATCH 4/8] Main function of ext4 online defrag and ioctl implementation
>> - Create the temporary inode and do defrag per
>>   defrag_size (defalut 64MB).
>>
> 
> I am curious about the ordering here. It seems reverse the order of the
> first 4 patches make the logic more clear to me, start from patch 4,
> then 3, then 2 and last 1?  At lease when I read the describtion of the
> first patch I was puzzled by a minute what is this coming from
> 
> Just share my thoughts.
> 

Ah, as you said, the ordering the patches is confusing.
I'll reconstruct my patches order(4-3-2-1-5-6-7-8) to be clear
in the future release.

Thanks,
Akira

      reply	other threads:[~2008-04-14  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 11:19 [RFC][PATCH 0/8] ext4 online defrag (ver 0.8) Akira Fujita
2008-04-11 20:18 ` Mingming Cao
2008-04-14  4:14   ` 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=4802DA0D.4060502@rs.jp.nec.com \
    --to=a-fujita@rs.jp.nec.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@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 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.