public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Takashi Sato" <sho@tnes.nec.co.jp>
To: "Joel Becker" <Joel.Becker@oracle.com>,
	"Andreas Dilger" <adilger@clusterfs.com>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-ext4@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/3] ext4 online defrag (ver 0.2)
Date: Wed, 17 Jan 2007 20:23:27 +0900	[thread overview]
Message-ID: <02bb01c73a29$eb846120$4168010a@bsd.tnes.nec.co.jp> (raw)
In-Reply-To: 20070116192134.GB5236@schatzie.adilger.int

Hi,

> On Jan 16, 2007  21:03 +0900, sho@tnes.nec.co.jp wrote:
>> 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...

>> struct ext4_ext_defrag_data {
>>         loff_t start_offset; /* start offset to defrag in byte */
>>         loff_t defrag_size;  /* size of defrag in bytes */
>> ext4_fsblk_t goal;   /* block offset for allocation */
>> };
>
> Two things of note:
> - presumably the start_offset and defrag_size should be multiples of the
>  filesystem blocksize?  If they are not, is it an error or are they
>  adjusted to cover whole blocks?

Given the value which isn't multiples of the blocksize,
they are adjusted to cover whole blocks in the kernel.

But I think that it isn't clean that the unit of goal is different from
start_offset and defrag_size.  I will change their unit into a blocksize
in the next update.

> - in previous defrag discussions (i.e. XFS defrag), it was desirable to
>  allow specifying different types of goals (e.g. hard, soft, kernel picks).
>  We may as well have a structure that allows these to be specified, instead
>  of having to change the interface afterward.

Let me see...  Is it the following discussion?
http://marc.theaimsgroup.com/?l=linux-ext4&m=116161490908645&w=2
http://marc.theaimsgroup.com/?l=linux-ext4&m=116184475306761&w=2

Cheers, Takashi

  parent reply	other threads:[~2007-01-17 11:23 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 [this message]
2007-01-19  5:19     ` Takashi Sato
2007-01-19 11:33       ` Andreas Dilger
2007-01-19 12:00         ` Takashi Sato

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='02bb01c73a29$eb846120$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