From: NeilBrown <neilb@suse.de>
To: David Heidelberger <david.heidelberger@ixit.cz>
Cc: Al Viro <viro@zeniv.linux.org.uk>, linux-nfs@vger.kernel.org
Subject: Re: DNOTIFY to INOTIFY migration
Date: Thu, 13 Mar 2014 10:11:58 +1100 [thread overview]
Message-ID: <20140313101158.5d857a2a@notabene.brown> (raw)
In-Reply-To: <8ecb362fb052a6dd1d1d1899fd38783f@ixit.cz>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
On Wed, 12 Mar 2014 23:52:31 +0100 David Heidelberger
<david.heidelberger@ixit.cz> wrote:
> Neil, what you think? Should I try someway simplify this as Al proposed?
No, Al is just letting off steam.
He hates the *notify interfaces (not without reason) and wishes people would
avoid them where-ever possible.
However rpc_pipefs does implement these interfaces, and doesn't implement
'poll' on directories, so changing nfs-utils to use poll wouldn't help.
I really don't think there is any need to do anything. It works and there is
not expectation that it will every stop working, and no evidence that there
is any problem with how it works. So best to leave it alone.
NeilBrown
>
> Dne 2014-03-10 02:45, Al Viro napsal:
> > On Mon, Mar 10, 2014 at 11:56:59AM +1100, NeilBrown wrote:
> >
> >> > 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).
> >
> > ... or just adding ->poll() to the directory in question and using the
> > normal syscalls instead of all that weird crap.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-03-12 23:12 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
2014-03-10 1:45 ` Al Viro
2014-03-12 22:52 ` David Heidelberger
2014-03-12 23:11 ` NeilBrown [this message]
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=20140313101158.5d857a2a@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.