public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@novell.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Steve French <smfrench@austin.rr.com>, linux-kernel@vger.kernel.org
Subject: Re: which ioctls matter across filesystems
Date: Fri, 29 Apr 2005 16:03:53 -0400	[thread overview]
Message-ID: <1114805033.6682.150.camel@betsy> (raw)
In-Reply-To: <1114804426.12692.49.camel@lade.trondhjem.org>

On Fri, 2005-04-29 at 15:53 -0400, Trond Myklebust wrote:

> We are discussing the equivalent of dnotify as a potential candidate for
> the first minor version of NFSv4, but not inotify.
> The purpose of our dnotify implementation is address the needs of things
> like file browsers that don't really care about synchronous notification
> of changes, but that do currently cause a lot of unnecessary traffic on
> the wire due to constantly polling stat() and doing readdir() updates.
> The jury is still out as to whether or not the callbacks actually do
> reduce on-the-wire traffic, though, so we may drop it.

What about inotify makes it insufficient for your needs?

> What kind of real-world applications exist out there that need inotify
> functionality, and what sort of requirements do they have (in particular
> w.r.t. the notification mechanism)?

A few worksets:

	- Current users, such as FAM and Samba, that need simple file
	  change notification
	- Random applications that want to watch a file or two
	- The Linux desktop
	- Real-time live-updating indexing systems, such as Beagle,
	  that compete with f.e. Apple's Spotlight.

Best,

	Robert Love



  reply	other threads:[~2005-04-29 20:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 19:22 which ioctls matter across filesystems Steve French
2005-04-29 19:53 ` Trond Myklebust
2005-04-29 20:03   ` Robert Love [this message]
2005-04-29 20:42     ` Trond Myklebust
2005-04-29 20:47       ` Robert Love
2005-04-29 21:13         ` Trond Myklebust
2005-04-29 21:22           ` Steve French
2005-04-29 21:38             ` Trond Myklebust
2005-04-29 20:55       ` Steve French
2005-04-29 20:57         ` Robert Love
2005-04-29 21:05           ` Steve French
2005-04-29 20:47     ` Steve French
2005-04-29 20:50       ` Robert Love
2005-04-29 21:00         ` Steve French
2005-04-29 20:32   ` Steve French

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=1114805033.6682.150.camel@betsy \
    --to=rml@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@austin.rr.com \
    --cc=trond.myklebust@fys.uio.no \
    /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