From: NeilBrown <neilb@suse.com>
To: Frank Filz <ffilzlnx@mindspring.com>,
'Jeff Layton' <jlayton@kernel.org>,
"'J. Bruce Fields'" <bfields@fieldses.org>
Cc: 'Alexander Viro' <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
'Martin Wilck' <mwilck@suse.de>
Subject: RE: [PATCH 0/4] locks: avoid thundering-herd wake-ups
Date: Thu, 09 Aug 2018 12:52:01 +1000 [thread overview]
Message-ID: <87600ktfou.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <01c401d42f70$5c034db0$1409e910$@mindspring.com>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
On Wed, Aug 08 2018, Frank Filz wrote:
>
> Now here's another question... How does this new logic play with Open
> File Description Locks? Should still be ok since there's a thread
> waiting on each of those.
At this level Posix locks and OFD locks are almost identical - just a
different owner.
So this enhancement should work equally for posix, flock, ofd and even
leases.
Thanks,
NeilBrown
>
> Frank
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-08-09 2:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 1:51 [PATCH 0/4] locks: avoid thundering-herd wake-ups NeilBrown
2018-08-08 1:51 ` [PATCH 1/4] fs/locks: rename some lists and pointers NeilBrown
2018-08-08 10:47 ` Jeff Layton
2018-08-08 19:07 ` J. Bruce Fields
2018-08-08 1:51 ` [PATCH 3/4] fs/locks: change all *_conflict() functions to return bool NeilBrown
2018-08-08 1:51 ` [PATCH 2/4] fs/locks: allow a lock request to block other requests NeilBrown
2018-08-08 1:51 ` [PATCH 4/4] fs/locks: create a tree of dependent requests NeilBrown
2018-08-08 16:47 ` [PATCH 0/4] locks: avoid thundering-herd wake-ups Jeff Layton
2018-08-08 18:29 ` J. Bruce Fields
2018-08-09 0:58 ` NeilBrown
2018-08-20 11:02 ` Martin Wilck
2018-08-20 20:02 ` J. Bruce Fields
2018-08-20 20:06 ` Martin Wilck
2018-08-08 19:54 ` J. Bruce Fields
2018-08-08 20:09 ` J. Bruce Fields
2018-08-08 21:15 ` Frank Filz
2018-08-08 22:34 ` NeilBrown
2018-08-08 21:28 ` J. Bruce Fields
2018-08-08 22:39 ` NeilBrown
2018-08-08 22:50 ` Jeff Layton
2018-08-08 23:34 ` Frank Filz
2018-08-09 2:52 ` NeilBrown [this message]
2018-08-09 13:00 ` J. Bruce Fields
2018-08-09 14:49 ` Jeff Layton
2018-08-09 23:56 ` NeilBrown
2018-08-10 1:05 ` 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=87600ktfou.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=bfields@fieldses.org \
--cc=ffilzlnx@mindspring.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwilck@suse.de \
--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 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).