From: Eric <erpo41@gmail.com>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [RFC] System calls for online defrag
Date: Wed, 05 Sep 2007 14:31:47 -0700 [thread overview]
Message-ID: <1189027907.13189.3.camel@eric-laptop> (raw)
In-Reply-To: <20070905142438.GB24462@duck.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
On Wed, 2007-09-05 at 16:24 +0200, Jan Kara wrote:
> On Tue 04-09-07 12:01:53, Andreas Dilger wrote:
> > On Sep 03, 2007 20:03 +0200, Jan Kara wrote:
> > > I've finally got to writing up some proposal how could look system calls
> > > allowing for online filesystem defragmentation and generally moving file
> > > blocks around for improving performance. Comments are welcome.
> > >
> > > int sys_movedata(int datafd, int spacefd, loff_t from, size_t len)
> > > The call takes blocks used to carry data starting at offset @from of length
> > > @len in @spacefd and places them instead of corresponding blocks in @datafd.
> >
> > Calling these "@spacefd" and "@datafd" is a bit confusing. How about "@srcfd"
> > and "@tgtfd" instead? For defragmentation, are you planning to have @datafd
> > be the "real" inode and "@spacefd" be the temporary inode with defragged data,
> > or the reverse? It isn't really clear.
> The idea behind the names was that you move data from @datafd into blocks
> provided by @spacefd. Calling it @srcfd and @tgtfd has the problem whether
> you mean source of data or source of blocks...
FWIW, I think @srcfd and @tgtfd are clearer.
When I think about changing the block on the disk that's associated with
a block's worth of data in a file, I think about scooping the file data
out of the source block and setting it down in the destination block. I
do not think about pulling the on-disk block out from under the data and
replacing it with a different on-disk block.
Cheers,
Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-09-05 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 18:03 [RFC] System calls for online defrag Jan Kara
2007-09-04 18:01 ` Andreas Dilger
2007-09-05 14:24 ` Jan Kara
2007-09-05 21:31 ` Eric [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=1189027907.13189.3.camel@eric-laptop \
--to=erpo41@gmail.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