From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Oleg Drokin <green@linuxhacker.ru>,
Mark Fasheh <mfasheh@suse.com>,
linux-fsdevel@vger.kernel.org, Sage Weil <sage@newdream.net>,
Andreas Dilger <adilger@sun.com>
Subject: Re: [PATCH 1/2] [RFC] vfs: 'stat light' fstatat flags
Date: Thu, 09 Apr 2009 11:13:35 -0400 [thread overview]
Message-ID: <1239290015.14159.8.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090408184842.GB10947@shareable.org>
On Wed, 2009-04-08 at 19:48 +0100, Jamie Lokier wrote:
> (Actually I'd like dnotify/inotify/fsnotify so I can omit the stat()
> round trip entirely please on each application cache
> revalidation... but only if "check for any file change events, answer
> = no events" is synchronous in the same way that AT_STRICT is...)
There is no protocol support for inotify or fsnotify.
The NFSv4.1 protocol does support a dnotify-ish callback, but that isn't
synchronous due to scalability concerns. It should be quite sufficient
for the likes of konqueror or nautilus, though...
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
prev parent reply other threads:[~2009-04-09 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 8:00 [PATCH 1/2] [RFC] vfs: 'stat light' fstatat flags Mark Fasheh
2009-04-07 10:23 ` Andreas Dilger
2009-04-07 14:59 ` Oleg Drokin
2009-04-07 15:18 ` Sage Weil
2009-04-07 15:29 ` Mark Fasheh
2009-04-07 17:52 ` Andreas Dilger
2009-04-07 18:13 ` Jamie Lokier
2009-04-07 23:13 ` Russell Cattelan
2009-04-07 17:42 ` Jamie Lokier
2009-04-07 17:48 ` Oleg Drokin
2009-04-07 18:16 ` Jamie Lokier
2009-04-07 18:24 ` Oleg Drokin
2009-04-07 20:37 ` Trond Myklebust
2009-04-08 18:48 ` Jamie Lokier
2009-04-09 15:13 ` Trond Myklebust [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=1239290015.14159.8.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=adilger@sun.com \
--cc=green@linuxhacker.ru \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=sage@newdream.net \
/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).