From: NeilBrown <neilb@suse.com>
To: Thomas Graf <tgraf@suug.ch>, Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Three rhashtable improvements
Date: Thu, 14 Mar 2019 16:05:28 +1100 [thread overview]
Message-ID: <155253979234.5022.1840929790507376038.stgit@noble.brown> (raw)
These three patches have previously been posted, but at the end of a
set where some early patches were contentious.
These patches did not depend on the others, so I'm posting them
separately.
The second patch has been changed slightly to make use of the new
API that Paul McKenney provided to check is call_rcu() has been
called yet or not.
Thanks,
NeilBrown
---
NeilBrown (3):
rhashtable: use cmpxchg() in nested_table_alloc()
rhashtable: don't hold lock on first table throughout insertion.
rhashtable: rename rht_for_each*continue as *from.
.clang-format | 8 +++---
include/linux/rhashtable.h | 53 +++++++++++++++------------------------
lib/rhashtable.c | 60 +++++++++++++++-----------------------------
3 files changed, 45 insertions(+), 76 deletions(-)
--
Signature
next reply other threads:[~2019-03-14 5:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 5:05 NeilBrown [this message]
2019-03-14 5:05 ` [PATCH 1/3] rhashtable: use cmpxchg() in nested_table_alloc() NeilBrown
2019-03-15 5:10 ` Herbert Xu
2019-03-15 6:51 ` NeilBrown
2019-03-20 5:41 ` Herbert Xu
2019-03-14 5:05 ` [PATCH 3/3] rhashtable: rename rht_for_each*continue as *from NeilBrown
2019-03-15 5:49 ` Herbert Xu
2019-03-17 7:50 ` Miguel Ojeda
2019-03-18 0:15 ` NeilBrown
2019-03-14 5:05 ` [PATCH 2/3] rhashtable: don't hold lock on first table throughout insertion NeilBrown
2019-03-14 14:58 ` Paul E. McKenney
2019-03-15 5:47 ` Herbert Xu
2019-03-15 6:46 ` NeilBrown
2019-03-20 5:40 ` Herbert Xu
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=155253979234.5022.1840929790507376038.stgit@noble.brown \
--to=neilb@suse.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tgraf@suug.ch \
/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
all inboxes | Powered by JetHome®