From: NeilBrown <neilb@suse.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: David Heidelberger <david.heidelberger@ixit.cz>,
linux-nfs@vger.kernel.org
Subject: Re: DNOTIFY to INOTIFY migration
Date: Mon, 10 Mar 2014 11:56:59 +1100 [thread overview]
Message-ID: <20140310115659.098a7c06@notabene.brown> (raw)
In-Reply-To: <20140310002015.GH18016@ZenIV.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On Mon, 10 Mar 2014 00:20:15 +0000 Al Viro <viro@ZenIV.linux.org.uk> wrote:
> On Mon, Mar 10, 2014 at 10:21:02AM +1100, NeilBrown wrote:
> > On Fri, 07 Mar 2014 21:30:34 +0100 David Heidelberger
> > <david.heidelberger@ixit.cz> wrote:
> >
> > > Hello,
> > >
> > > in linux kernel is DNOTIFY actually marked as deprecated, with superior
> > > replacement INOTIFY.
> >
> > Where is it marked as deprecated? I would be very surprised if dnotify
> > wasn't supported indefinitely.
>
> Unfortunately, it will be - once it's in, it's in.
>
> > (I have no opinion on whether rpc.idmapd should be changed to use inotify,
> > except based on the "if it ain't broke, don't fix it" principle).
>
> I still don't understand WTF does rpc.imapd *want* either of those, TBH.
The rpc_pipefs filesysem which is mounted on /var/lib/nfs/rpc_pipefs creates
new channels for talking to userspace by making new pipes appear in some
directory. Any client needs to arrange some notification for these new pipes
appearing so that it can open them and hold a conversation over them.
This calls for dnotify (in gssd and idmapd) or inotify (in blkmapd).
NeilBrown
>
> Said that, the original posting does read a bit like "herpes is so last century,
> shouldn't we upgrade to clap by now?"...*0O(and I don't want to think what
> that makes fanotify, thank you very much)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-03-10 0:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 20:30 DNOTIFY to INOTIFY migration David Heidelberger
2014-03-09 23:21 ` NeilBrown
2014-03-10 0:20 ` Al Viro
2014-03-10 0:56 ` NeilBrown [this message]
2014-03-10 1:45 ` Al Viro
2014-03-12 22:52 ` David Heidelberger
2014-03-12 23:11 ` NeilBrown
2014-03-10 0:55 ` David Heidelberger
2014-03-10 0:15 ` NeilBrown
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=20140310115659.098a7c06@notabene.brown \
--to=neilb@suse.de \
--cc=david.heidelberger@ixit.cz \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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.