From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
NeilBrown <neilb@suse.com>, Thomas Graf <tgraf@suug.ch>,
Herbert Xu <herbert@gondor.apana.org.au>,
Tom Herbert <tom@quantonium.net>,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: [PATCH v2 0/2] gfs2: Stop using rhashtable_walk_peek
Date: Thu, 29 Mar 2018 14:06:10 +0200 [thread overview]
Message-ID: <20180329120612.6104-1-agruenba@redhat.com> (raw)
Here's a second version of the patch (now a patch set) to eliminate
rhashtable_walk_peek in gfs2.
The first patch introduces lockref_put_not_zero, the inverse of
lockref_get_not_zero.
The second patch eliminates rhashtable_walk_peek in gfs2. In
gfs2_glock_iter_next, the new lockref function from patch one is used to
drop a lockref count as long as the count doesn't drop to zero. This is
almost always the case; if there is a risk of dropping the last
reference, we must defer that to a work queue because dropping the last
reference may sleep.
Thanks,
Andreas
Andreas Gruenbacher (2):
lockref: Add lockref_put_not_zero
gfs2: Stop using rhashtable_walk_peek
fs/gfs2/glock.c | 47 ++++++++++++++++++++++++++++-------------------
include/linux/lockref.h | 1 +
lib/lockref.c | 28 ++++++++++++++++++++++++++++
3 files changed, 57 insertions(+), 19 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-29 12:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 12:06 Andreas Gruenbacher [this message]
2018-03-29 12:06 ` [PATCH v2 1/2] lockref: Add lockref_put_not_zero Andreas Gruenbacher
2018-03-29 12:06 ` [PATCH v2 2/2] gfs2: Stop using rhashtable_walk_peek Andreas Gruenbacher
2018-03-29 12:24 ` [Cluster-devel] [PATCH v2 0/2] " Steven Whitehouse
2018-03-29 13:12 ` Andreas Gruenbacher
2018-03-29 12:35 ` Herbert Xu
2018-03-29 13:15 ` Andreas Gruenbacher
2018-03-29 15:41 ` Herbert Xu
2018-03-29 16:52 ` Andreas Gruenbacher
2018-03-29 17:06 ` Herbert Xu
2018-04-03 3:41 ` NeilBrown
2018-04-03 4:03 ` Herbert Xu
2018-04-04 15:46 ` [Cluster-devel] " Bob Peterson
2018-04-04 15:48 ` Herbert Xu
2018-04-04 16:10 ` Andreas Grünbacher
2018-04-06 1:33 ` [Cluster-devel] " NeilBrown
2018-04-12 17:00 ` Bob Peterson
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=20180329120612.6104-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=tom@quantonium.net \
/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).