From: Jeff Layton <jlayton@poochiereds.net>
To: "Matt W. Benjamin" <matt@linuxbox.com>
Cc: Ganesha NFS List <nfs-ganesha-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
"J. Bruce Fields" <bfields@fieldses.org>,
Neil Brown <neilb@suse.de>,
samba-technical@lists.samba.org, linux-nfs@vger.kernel.org,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
"Frank Filz" <ffilzlnx@mindspring.com>
Subject: Re: OFD ("file private") locks and NFS
Date: Tue, 29 Apr 2014 07:50:46 -0400 [thread overview]
Message-ID: <20140429075046.39fc9c3f@tlielax.poochiereds.net> (raw)
In-Reply-To: <1482413734.4.1398771608019.JavaMail.root@thunderbeast.private.linuxbox.com>
On Tue, 29 Apr 2014 07:40:08 -0400 (EDT)
"Matt W. Benjamin" <matt@linuxbox.com> wrote:
> Hi Jeff,
>
> Something which came up on the last Ganesha conn call is that we have
> a pretty strong need for some ability to wait on a set of locks, and perhaps
> receive events. Frank Filz believed that you had made a proposal which
> would cover this. Can you elaborate on that?
>
> Thanks,
>
> Matt
>
No, there's no mechanism to wait on a set of locks from within the
context of a single thread of execution or to receive "events". Again,
that would be a new API beyond what I've been proposing over the last
several months.
--
Jeff Layton <jlayton@poochiereds.net>
next prev parent reply other threads:[~2014-04-29 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 8:38 Michael Kerrisk (man-pages)
2014-04-29 8:47 ` Michael Kerrisk (man-pages)
2014-04-29 11:11 ` Jeff Layton
2014-04-29 11:15 ` Michael Kerrisk (man-pages)
2014-04-29 11:40 ` Matt W. Benjamin
2014-04-29 11:50 ` Jeff Layton [this message]
2014-04-29 15:11 ` Frank Filz
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=20140429075046.39fc9c3f@tlielax.poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=bfields@fieldses.org \
--cc=ffilzlnx@mindspring.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=matt@linuxbox.com \
--cc=mtk.manpages@gmail.com \
--cc=neilb@suse.de \
--cc=nfs-ganesha-devel@lists.sourceforge.net \
--cc=samba-technical@lists.samba.org \
--cc=trond.myklebust@fys.uio.no \
/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
all inboxes | Powered by JetHome®