public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Takashi Sato" <sho@tnes.nec.co.jp>
To: "Andreas Dilger" <adilger@clusterfs.com>
Cc: "Joel Becker" <Joel.Becker@oracle.com>,
	<linux-ext4@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/3] ext4 online defrag (ver 0.2)
Date: Fri, 19 Jan 2007 21:00:44 +0900	[thread overview]
Message-ID: <024c01c73bc1$75a31f20$4168010a@bsd.tnes.nec.co.jp> (raw)
In-Reply-To: 20070119113351.GM5236@schatzie.adilger.int

Hi,

Thank you for your comment.

>> >>>1. Add new ioctl(EXT4_IOC_DEFRAG) which returns the first physical
>> >>>   block number of the specified file.  With this ioctl, a command
>> >>>   gets the specified directory's.
>> >>
>> >>Maybe I don't understand, but how is this different from the long-time
>> >>FIBMAP ioctl?
>> >
>> >I can use FIBMAP instead of my new ioctl.
>> >You are right.  I should have used FIBMAP ioctl...
>>
>> I have to get the physical block number of the specified directory.
>> But FIBMAP is available only for a regular file, not for a directory.
>> So I will use my new ioctl.
>
> Though it might make sense to implement FIBMAP for a directory, to keep
> it consistent and allow user-space tools like "filefrag" to work on
> directories also.

It sounds good.
I think it will be useful for other tools which use FIBMAP.
So I will consider the implementation of FIBMAP for a directory.

Cheers, Takashi

      reply	other threads:[~2007-01-19 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16 12:03 [RFC][PATCH 0/3] ext4 online defrag (ver 0.2) sho
2007-01-16 19:21 ` Andreas Dilger
2007-01-16 20:41   ` Joel Becker
2007-01-17 11:23   ` Takashi Sato
2007-01-19  5:19     ` Takashi Sato
2007-01-19 11:33       ` Andreas Dilger
2007-01-19 12:00         ` Takashi Sato [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='024c01c73bc1$75a31f20$4168010a@bsd.tnes.nec.co.jp' \
    --to=sho@tnes.nec.co.jp \
    --cc=Joel.Becker@oracle.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@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