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:47:28 -0400 [thread overview]
Message-ID: <1114807648.6682.153.camel@betsy> (raw)
In-Reply-To: <1114807360.12692.77.camel@lade.trondhjem.org>
On Fri, 2005-04-29 at 16:42 -0400, Trond Myklebust wrote:
> The problem is that having the server call back a bunch of clients every
> time a file changes does not really scale too well. The current
> dnotify-like proposal therefore specifies that notification is not
> synchronous (i.e. there may be a delay of several seconds), and that the
> server may want to group several notifications into a single callback.
Yah, so what I am asking is why not use inotify for the user-side
component of this system?
Wouldn't the deferring and coalescing of events occur on the server
side? So the server-side stuff would be whatever you need--your own
code using whatever protocol you wanted--but the client-side interface
would be over inotify.
Even if not, I'd be willing to make changes to inotify to accommodate
NFS's needs.
Robert Love
next prev parent reply other threads:[~2005-04-29 20:50 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
2005-04-29 20:42 ` Trond Myklebust
2005-04-29 20:47 ` Robert Love [this message]
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=1114807648.6682.153.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.