linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Steve French <smfrench@gmail.com>,
	lsf-pc@lists.linux-foundation.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ioannis Angelakopoulos <jaggel@bu.edu>
Subject: Re: [LSF/MM/BPF TOPIC] Enabling change notification for network and cluster fs
Date: Fri, 25 Feb 2022 13:49:19 +0000	[thread overview]
Message-ID: <YhjeX0HvXbED65IM@casper.infradead.org> (raw)
In-Reply-To: <YhjYSMIE2NBZ/dGr@redhat.com>

On Fri, Feb 25, 2022 at 08:23:20AM -0500, Vivek Goyal wrote:
> What about local events. I am assuming you want to supress local events
> and only deliver remote events. Because having both local and remote
> events delivered at the same time will be just confusing at best.

This paragraph confuses me.  If I'm writing, for example, a file manager
and I want it to update its display automatically when another task alters
the contents of a directory, I don't care whether the modification was
done locally or remotely.

If I understand the SMB protocol correctly, it allows the client to take
out a lease on a directory and not send its modifications back to the
server until the client chooses to (or the server breaks the lease).
So you wouldn't get any remote notifications because the client hasn't
told the server.

  reply	other threads:[~2022-02-25 13:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  5:16 [LSF/MM/BPF TOPIC] Enabling change notification for network and cluster fs Steve French
2022-02-24 21:52 ` Vivek Goyal
2022-02-24 22:55   ` Steve French
2022-02-25 13:23     ` Vivek Goyal
2022-02-25 13:49       ` Matthew Wilcox [this message]
2022-02-25 14:30         ` Vivek Goyal
2022-02-25 15:27         ` Steve French
2022-02-25 16:35           ` Vivek Goyal
     [not found]             ` <CAH2r5msPz1JZK4OWX_=+2HTzKTZE07ACxbEv3xM-1T0HTnVWMw@mail.gmail.com>
2022-02-26 10:22               ` [Lsf-pc] " Amir Goldstein
2022-02-28  5:42                 ` Ralph Boehme
2022-02-26 16:44               ` Vivek Goyal
2022-03-11 12:36 ` Vivek Goyal

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=YhjeX0HvXbED65IM@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=jaggel@bu.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=smfrench@gmail.com \
    --cc=vgoyal@redhat.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).