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: Mon, 21 May 2007 19:25:37 +0900 [thread overview]
Message-ID: <019c01c79b92$627b3280$4168010a@bsd.tnes.nec.co.jp> (raw)
In-Reply-To: 464DA4ED.9040408@linux.vnet.ibm.com
Hi Aneesh san,
> While doing online defragmentation do we move the blocks corresponding to extent index ?
> The reason why i am asking this is to understand the
> usefulness of doing a ext4migrate followed by defrag. I understand that defragmentation
> in general will improve the performance. But with respect to ext4migrate we are not
> touching the data blocks. Instead we build the extent map and if that requires to have
> an extent index block then we allocate one. I am trying to understand what would be the
> performance impact of this and whether doing a defrag really improve the performance.
I think converting a file to extents has the benefit for the performance of
block searching. If we want to improve also the performance of reading
file data, we have to run the defrag after that.
> Also looking at the version 0.4 I see that defrag ioctl only work if we have
> EXT4_EXTENTS_FL flag set. What are the plans for making defrag work with indirect block
> map inode ?
Unfortunately, my defrag doesn't support an indirect block file.
But we can reduce fragments in the file with the defrag just after
ext4migrate.
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?
Cheers, Takashi
next prev parent reply other threads:[~2007-05-21 10:29 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 [this message]
2007-05-21 10:37 ` Aneesh Kumar K.V
2007-05-22 8:35 ` Takashi Sato
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='019c01c79b92$627b3280$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