From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm@osdl.org, Trond Myklebust <Trond.Myklebust@netapp.com>,
Marc Eshel <eshel@almaden.ibm.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 9/17] locks: add lock cancel command
Date: Tue, 10 Apr 2007 17:53:01 -0400 [thread overview]
Message-ID: <20070410215301.GL7502@fieldses.org> (raw)
In-Reply-To: <20070409184144.GB28716@infradead.org>
On Mon, Apr 09, 2007 at 07:41:44PM +0100, Christoph Hellwig wrote:
> On Thu, Apr 05, 2007 at 07:40:59PM -0400, J. Bruce Fields wrote:
> > We do this by adding a new fcntl lock command: FL_CANCELLK. Some day this
> > might also be made available to userspace applications that could benefit from
> > an asynchronous locking api.
>
> Should we really add more and more subcases to ->lock that probably don't
> share implementation code? I'd much prefer adding different operations.
That'd be OK. We considered both--
http://marc.info/?l=linux-fsdevel&m=116616992004056&w=2
--but chose a new ->lock case just because that might provide a cleaner
mapping to the userspace interface if we ended up doing that some day.
Is there any hard reason why it wouldn't work?
--b.
next prev parent reply other threads:[~2007-04-10 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 18:41 [PATCH 9/17] locks: add lock cancel command Christoph Hellwig
2007-04-10 21:53 ` J. Bruce Fields [this message]
[not found] <117581646786-git-send-email->
[not found] ` <11758164673642-git-send-email->
[not found] ` <11758164671398-git-send-email->
[not found] ` <11758164672114-git-send-email->
[not found] ` <11758164672880-git-send-email->
[not found] ` <1175816467294-git-send-email->
[not found] ` <11758164671240-git-send-email->
[not found] ` <11758164686-git-send-email->
[not found] ` <1175816468241-git-send-email->
2007-04-05 23:40 ` J. Bruce Fields
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=20070410215301.GL7502@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@osdl.org \
--cc=eshel@almaden.ibm.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
/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