From: Andreas Dilger <adilger@sun.com>
To: Jan Kara <jack@suse.cz>
Cc: Abhijit Paithankar <apaithan@akamai.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Jamie Lokier <jamie@shareable.org>,
Dave Chinner <david@fromorbit.com>
Subject: Re: [RFC PATCH] Filesystem Journal Notifications
Date: Tue, 23 Sep 2008 16:26:26 -0600 [thread overview]
Message-ID: <20080923222626.GP10950@webber.adilger.int> (raw)
In-Reply-To: <20080920051537.GC9633@atrey.karlin.mff.cuni.cz>
On Sep 20, 2008 07:15 +0200, Jan Kara wrote:
> 1) At the first sight it seems to be a useful idea to send to
> userspace notifications when some change is safely on disk. But at the
> second sight, it's technically really not that simple as it may seem.
> Filesystems such as ext2 have no good way of providing such information,
> even ext4 with delayed allocation has no way of giving you such
> information for writes and I guess similar thing holds for xfs. Also log
> structured filesystems and similar can tell you when a change is safely
> on disk but have no concept of something like journal commit. So at this
> point one should really ask himself whether a feature having a chance to
> work only on a limited number of setups has a serious chance of being
> used by application developpers...
> Also note that on ext3 and ext4 a single 'write' call from userspace
> can be split among several transactions but there's just one inotify
> event so this has to be taken care of.
I think the assumption is that this isn't an API used by "generic"
applications, but rather ones that are being optimized for the system
they are running on. ext3/4 is common enough that this isn't a very
limiting optimization. I don't think Akamai are going to care about
running on JFFS2 or VFAT. Probably registering for such events on
filesystems that don't understand them should just return an error.
We'll be stuck in 1981 forever if we continue to limit interfaces to
what all filesystems understand.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-09-23 22:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 22:06 [RFC PATCH] Filesystem Journal Notifications Abhijit Paithankar
2008-09-13 9:19 ` Dave Chinner
2008-09-15 2:31 ` Andreas Dilger
2008-09-15 5:39 ` Andreas Dilger
2008-09-15 19:36 ` Abhijit Paithankar
2008-09-15 23:37 ` Andreas Dilger
2008-09-16 23:05 ` Abhijit Paithankar
2008-09-19 20:34 ` Andreas Dilger
2008-09-20 15:51 ` Jamie Lokier
2008-09-20 5:15 ` Jan Kara
2008-09-23 22:26 ` Andreas Dilger [this message]
2008-09-15 13:23 ` Jamie Lokier
2008-09-17 0:06 ` Abhijit Paithankar
2008-09-17 11:35 ` Jamie Lokier
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=20080923222626.GP10950@webber.adilger.int \
--to=adilger@sun.com \
--cc=apaithan@akamai.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=jamie@shareable.org \
--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;
as well as URLs for NNTP newsgroup(s).