From: Eric Sandeen <sandeen@redhat.com>
To: Avantika Mathur <mathur@us.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 devel interlock meeting minutes (Nov. 22 2006)
Date: Wed, 22 Nov 2006 21:33:16 -0600 [thread overview]
Message-ID: <4565167C.4060802@redhat.com> (raw)
In-Reply-To: <1164232428.29430.27.camel@dyn9047017105.beaverton.ibm.com>
Avantika Mathur wrote:
> Ext4 Developer Interlock Call: 11/22/06 minutes
>
> Attendees: Mingming Cao, Eric Sandeen, Suparna Bhattacharya, Takashi Sato, Jean-Pierre Dion, Valérie Clément, Avantika Mathur
>
> - Online Defrag:
> -- Last week we determined that ioctl was the preferred
> interface for the online defrag.
> -- Eric will send out an ovreview of the steps completed by XFS for file defragmentation.
> -- Last week Eric said that in XFS defrag implementation, you can't defrag a file that is open/being written to. This was an incorrect assumption. There will be more explanation in his mail.
>
> - Preallocation:
> -- We need to decide which interface to use in the implementation
> * ioctl: simple solution preferred method for defrag and user in reservation
And would also be useful for testing, at least. If reiserfs or jfs or
xfs has existing interfaces for preallocation that are at all useful,
perhaps we could even piggyback on them for now, in the same way that
other filesystems picked up ext[23]'s chattr interfaces?
> * posix_fallocate: writes zero to the first byte of every block; probably preferred solution
For the record, this is only how glibc does it today, it certainly
doesn't have to be done this way, ideally a kernel syscall which allows
filesystems to be smart would be best. Coordinating glibc & kernel
changes will be tricky & time consuming though... but it's a noble goal.
I'd like to see it happen; I'll chat with Ulrich when I get a chance,
see what he thinks.
> * ftruncate: consistency across platforms may be an issue
I agree w/ Andreas on this, I don't see how ftruncate can be used w/o
making holey files impossible.
-Eric
prev parent reply other threads:[~2006-11-23 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 21:53 Ext4 devel interlock meeting minutes (Nov. 22 2006) Avantika Mathur
2006-11-23 1:13 ` Andreas Dilger
2006-11-23 3:33 ` Eric Sandeen [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=4565167C.4060802@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mathur@us.ibm.com \
/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).