From: Vivek Goyal <vgoyal@redhat.com>
To: Steve French <smfrench@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] Enabling change notification for network and cluster fs
Date: Fri, 11 Mar 2022 07:36:13 -0500 [thread overview]
Message-ID: <YitCPVmurnC5Re9D@redhat.com> (raw)
In-Reply-To: <CAH2r5mt9OfU+8PoKsmv_7aszhbw-dOuDCL6BOxb_2yRwc4HHCw@mail.gmail.com>
On Wed, Feb 23, 2022 at 11:16:33PM -0600, Steve French wrote:
> Currently only local events can be waited on with the current notify
> kernel API since the requests to wait on these events is not passed to
> the filesystem. Especially for network and cluster filesystems it is
> important that they be told that applications want to be notified of
> these file or directory change events.
>
> A few years ago, discussions began on the changes needed to enable
> support for this. Would be timely to finish those discussions, as
> waiting on file and directory change events to network mounts is very
> common for other OS, and would be valuable for Linux to fix.
If this topic gets selected for discussion, I will be interested in
joining the conversation.
Vivek
>
> --
> Thanks,
>
> Steve
>
prev parent reply other threads:[~2022-03-11 12:36 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
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 [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=YitCPVmurnC5Re9D@redhat.com \
--to=vgoyal@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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 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.