linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Steve French <smfrench@gmail.com>,
	linux-cifs-client@lists.samba.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] cifs: remove dnotify thread code
Date: Sat, 10 Jan 2009 01:41:28 +0000	[thread overview]
Message-ID: <20090110014128.GF1972@shareable.org> (raw)
In-Reply-To: <20090108202824.69fcac39@tleilax.poochiereds.net>

Jeff Layton wrote:
> > I think NFSv4 can do it with delegations, although the exact semantics
> > an app could rely on would be different.
> 
> I don't think delegations help here since it's entirely up to the
> server whether to grant one or not. I've only given inotify/dnotify a
> drive-by look, but I'm pretty sure you'd want the client to be able to
> set up events to monitor.

The notify API needs the ability to report, in general, whether you'll
get notify events from a particular filesystem / file / directory /
whatever-condition anyway.  And also whether you get events for all
(remote) changes, or just local changes.

You might as well _try_ to get a delegate, and if you fail, tell the
caller that it won't receive notifications on this file and will have
to poll - just like most other remote filesystems.

-- Jamie

  parent reply	other threads:[~2009-01-10  1:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 14:15 [PATCH] cifs: remove dnotify thread code Jeff Layton
2009-01-08 14:23 ` Steve French
2009-01-08 14:51   ` Jeff Layton
2009-01-09  0:07   ` Jamie Lokier
2009-01-09  1:28     ` Jeff Layton
2009-01-10  1:35       ` Jamie Lokier
2009-01-10  1:41       ` Jamie Lokier [this message]
2009-01-10 18:19         ` Steve French
2009-01-09  3:32     ` Steve French
2009-01-09 11:33       ` Jeff Layton
2009-01-09 16:18         ` Steve French
2009-01-09 18:07           ` Jeff Layton
2009-01-09 18:18       ` Al Viro

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=20090110014128.GF1972@shareable.org \
    --to=jamie@shareable.org \
    --cc=jlayton@redhat.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=smfrench@gmail.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).