From: Joel Becker <Joel.Becker@oracle.com>
To: sho@tnes.nec.co.jp, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/3] ext4 online defrag (ver 0.2)
Date: Tue, 16 Jan 2007 12:41:52 -0800 [thread overview]
Message-ID: <20070116204152.GI27360@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20070116192134.GB5236@schatzie.adilger.int>
On Tue, Jan 16, 2007 at 12:21:34PM -0700, Andreas Dilger wrote:
> On Jan 16, 2007 21:03 +0900, sho@tnes.nec.co.jp wrote:
> > 2. The new entry "goal" is added on ext4_ext_defrag_data structure
> > which is passed to existing ioctl(EXT4_IOC_DEFRAG)
> > as the argument. The kernel starts searching the free blocks
> > from "goal". The command passes the physical block number
> > gotten in the above step(1) to the 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?
In fact, why aren't the units in blocks? THe filesystem isn't
really going to deal with anything smaller, is it?
Joel
--
Life's Little Instruction Book #335
"Every so often, push your luck."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2007-01-16 20:41 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 [this message]
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
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=20070116204152.GI27360@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sho@tnes.nec.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).