From: "Takashi Sato" <sho@tnes.nec.co.jp>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: <linux-ext4@vger.kernel.org>
Subject: Re: Online defragmentation and ext4migrate
Date: Tue, 22 May 2007 17:35:09 +0900 [thread overview]
Message-ID: <025e01c79c4c$1e1eefe0$4168010a@bsd.tnes.nec.co.jp> (raw)
In-Reply-To: 46517669.50804@linux.vnet.ibm.com
Hi,
>> In my opinion, to keep the ioctl simple and small is very important
>> for ease of maintenance. So I would rather not support indirect
>> block files in the ioctl.
>> Instead, I can add the call of the migration ioctl to my defrag tool in order
>> to defragment indirect block files. How do you think of it?
>>
>
> That should be fine. So i will start moving the ext4migrate code as a ext4 ioctl and
> later will send you a patch to the defrag tool that will migrate and defrag.
OK. I am looking forward to your patch.
Cheers, Takashi
next prev parent reply other threads:[~2007-05-22 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 13:06 Online defragmentation and ext4migrate Aneesh Kumar K.V
2007-05-18 20:19 ` Eric
2007-05-18 21:05 ` Andreas Dilger
2007-05-21 8:33 ` Aneesh Kumar
2007-05-21 10:42 ` Jan Kara
2007-05-21 10:25 ` Takashi Sato
2007-05-21 10:37 ` Aneesh Kumar K.V
2007-05-22 8:35 ` Takashi Sato [this message]
2007-05-21 10:38 ` Jan Kara
2007-05-21 13:36 ` Eric
2007-05-22 11:28 ` Jan Kara
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='025e01c79c4c$1e1eefe0$4168010a@bsd.tnes.nec.co.jp' \
--to=sho@tnes.nec.co.jp \
--cc=aneesh.kumar@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox