From: NeilBrown <neilb@suse.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Martin Wilck <mwilck@suse.de>,
linux-fsdevel@vger.kernel.org,
Frank Filz <ffilzlnx@mindspring.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 00/12 v6] fs/locks: avoid thundering-herd wake-ups
Date: Fri, 30 Nov 2018 10:04:08 +1100 [thread overview]
Message-ID: <154353251599.32133.1085882002675619240.stgit@noble> (raw)
This series has the fixes for the recently reported performance
regressions merged into the patches which caused them.
It also has a couple of little fixes that have been mentioned on the
list, and that Jeff had merged into his copy.
Thanks,
NeilBrown
---
NeilBrown (12):
fs/locks: rename some lists and pointers.
fs/locks: split out __locks_wake_up_blocks().
NFS: use locks_copy_lock() to copy locks.
gfs2: properly initial file_lock used for unlock.
ocfs2: properly initial file_lock used for unlock.
fs/locks: use properly initialized file_lock when unlocking.
fs/locks: allow a lock request to block other requests.
fs/locks: always delete_block after waiting.
fs/locks: change all *_conflict() functions to return bool.
fs/locks: create a tree of dependent requests.
fs/locks: merge posix_unblock_lock() and locks_delete_block()
fs/locks: locks: remove unnecessary white space.
fs/cifs/file.c | 4
fs/gfs2/file.c | 10 +
fs/lockd/svclock.c | 2
fs/locks.c | 342 +++++++++++++++++++++++++--------------
fs/nfs/nfs4proc.c | 6 -
fs/nfsd/nfs4state.c | 6 -
fs/ocfs2/locks.c | 10 +
include/linux/fs.h | 13 +
include/trace/events/filelock.h | 16 +-
9 files changed, 252 insertions(+), 157 deletions(-)
--
Signature
next reply other threads:[~2018-11-30 10:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 23:04 NeilBrown [this message]
2018-11-29 23:04 ` [PATCH 11/12] fs/locks: merge posix_unblock_lock() and locks_delete_block() NeilBrown
2018-11-29 23:04 ` [PATCH 10/12] fs/locks: create a tree of dependent requests NeilBrown
2018-11-29 23:04 ` [PATCH 09/12] fs/locks: change all *_conflict() functions to return bool NeilBrown
2018-11-29 23:04 ` [PATCH 03/12] NFS: use locks_copy_lock() to copy locks NeilBrown
2018-11-29 23:04 ` [PATCH 04/12] gfs2: properly initial file_lock used for unlock NeilBrown
2018-11-29 23:04 ` [PATCH 02/12] fs/locks: split out __locks_wake_up_blocks() NeilBrown
2018-11-29 23:04 ` [PATCH 08/12] fs/locks: always delete_block after waiting NeilBrown
2018-11-29 23:04 ` [PATCH 05/12] ocfs2: properly initial file_lock used for unlock NeilBrown
2018-11-29 23:04 ` [PATCH 01/12] fs/locks: rename some lists and pointers NeilBrown
2018-11-29 23:04 ` [PATCH 07/12] fs/locks: allow a lock request to block other requests NeilBrown
2018-11-29 23:04 ` [PATCH 12/12] fs/locks: remove unnecessary white space NeilBrown
2018-11-29 23:04 ` [PATCH 06/12] fs/locks: use properly initialized file_lock when unlocking NeilBrown
2018-11-30 16:34 ` [PATCH 00/12 v6] fs/locks: avoid thundering-herd wake-ups Jeff Layton
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=154353251599.32133.1085882002675619240.stgit@noble \
--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 \
/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