From: simo <idra@samba.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Stef Bon <stefbon@gmail.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: Possible to make nfs aware of a inotify watch has been set.
Date: Thu, 29 Nov 2012 17:26:38 -0500 [thread overview]
Message-ID: <1354227998.4064.11.camel@pico.ipa.ssimo.org> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA90B32D9D4@SACEXCMBX04-PRD.hq.netapp.com>
On Thu, 2012-11-29 at 21:09 +0000, Myklebust, Trond wrote:
> On Thu, 2012-11-29 at 15:05 -0500, simo wrote:
> > On Thu, 2012-11-29 at 17:11 +0000, Myklebust, Trond wrote:
> > > The idea that "if we build a bridge, they will come to us" is what
> > > gave
> > > rise to dnotify, then inotify (nobody came, so let's build a bigger
> > > bridge) and fsnotify (make it a toll bridge). Nobody is using those
> > > interfaces much on local filesystems, so why is adding it to NFS and
> > > CIFS going to be such a game changer?
> >
> > Sorry Trond,
> > but this is simply not true.
> >
> > inotify is a key feature at least in some packages I know, and makes
> > some things *a lot* easier.
> >
> > Of course this are less visible features, that are easy to overlook, but
> > they are not unused for sure.
>
> So why is it so difficult for anyone in this thread to name these killer
> applications that would benefit from NFS+CIFS support? I keep asking,
> and all I get is wishy-washy and hand-wavy answers.
>
> Without use cases, there is nothing to discuss on the implementation
> front.
Sorry for the misunderstanding, I wasn't talking about inotify *on
CIFS/NFS*, I do not care about that use case, I'll gladly let Stef pitch
it for himself :)
Simo.
--
Simo Sorce
Samba Team GPL Compliance Officer <simo@samba.org>
Principal Software Engineer at Red Hat, Inc. <simo@redhat.com>
next prev parent reply other threads:[~2012-11-29 22:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 9:32 Possible to make nfs aware of a inotify watch has been set Stef Bon
2012-11-29 14:03 ` Myklebust, Trond
2012-11-29 14:49 ` Stef Bon
2012-11-29 14:54 ` Myklebust, Trond
2012-11-29 15:22 ` simo
2012-11-29 15:33 ` Myklebust, Trond
2012-11-29 16:28 ` Steve French
2012-11-29 17:05 ` Myklebust, Trond
2012-11-29 16:39 ` Stef Bon
2012-11-29 17:11 ` Myklebust, Trond
2012-11-29 20:05 ` simo
2012-11-29 21:09 ` Myklebust, Trond
2012-11-29 22:26 ` simo [this message]
2012-11-29 20:10 ` Stef Bon
2012-11-29 20:20 ` Al Viro
2012-11-29 20:31 ` Stef Bon
2012-11-29 21:16 ` Al Viro
2012-11-29 23:14 ` Stef Bon
2012-11-29 23:44 ` Steve French
2012-11-30 7:10 ` Stef Bon
2012-11-30 7:19 ` Stef Bon
2012-11-30 13:37 ` Bernd Petrovitsch
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=1354227998.4064.11.camel@pico.ipa.ssimo.org \
--to=idra@samba.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=stefbon@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).