linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Jeff Layton <jlayton@poochiereds.net>
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>
Subject: Re: OFD ("file private") locks and NFS
Date: Tue, 29 Apr 2014 07:40:08 -0400 (EDT)	[thread overview]
Message-ID: <1482413734.4.1398771608019.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <20140429071153.176c7404@tlielax.poochiereds.net>

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

----- "Jeff Layton" <jlayton@poochiereds.net> wrote:

> 
> If we really find later that we need to do something like this, I
> think
> we'd be better off adding a new set of cmd values along with the
> "extended" struct, or possibly a new syscall. Some of the samba folks
> were interested in an async locking mechanism too, so something like
> that could be added in conjunction with such an interface.
> 


-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

  parent reply	other threads:[~2014-04-29 11:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <535F651E.6090204@gmail.com>
2014-04-29  8:47 ` OFD ("file private") locks and NFS 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 [this message]
2014-04-29 11:50       ` Jeff Layton
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=1482413734.4.1398771608019.JavaMail.root@thunderbeast.private.linuxbox.com \
    --to=matt@linuxbox.com \
    --cc=bfields@fieldses.org \
    --cc=jlayton@poochiereds.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).