From: Thomas Graf <tgraf@suug.ch>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kaber@trash.net,
paulmck@linux.vnet.ibm.com, josh@joshtriplett.org,
challa@noironetworks.com, walpole@cs.pdx.edu,
dev@openvswitch.org
Subject: [PATCH 0/2 net-next] Lockless netlink_lookup() with new concurrent hash table
Date: Tue, 29 Jul 2014 13:41:31 +0200 [thread overview]
Message-ID: <cover.1406633945.git.tgraf@suug.ch> (raw)
Netlink sockets are maintained in a hash table to allow efficient lookup
via the port ID for unicast messages. However, lookups currently require
a read lock to be taken. This series adds a new generic, resizable,
scalable, concurrent hash table based on the paper referenced in the first
patch. It then makes use of the new data type to implement lockless
netlink_lookup().
Against net-next since the initial user of the new hash table is in net/
Thomas Graf (2):
lib: Resizable, Scalable, Concurrent Hash Table
netlink: Convert netlink_lookup() to use RCU protected hash table
include/linux/rhashtable.h | 208 ++++++++++++
lib/Kconfig.debug | 8 +
lib/Makefile | 2 +-
lib/rhashtable.c | 783 +++++++++++++++++++++++++++++++++++++++++++++
net/netlink/af_netlink.c | 285 +++++++----------
net/netlink/af_netlink.h | 18 +-
net/netlink/diag.c | 11 +-
7 files changed, 1119 insertions(+), 196 deletions(-)
create mode 100644 include/linux/rhashtable.h
create mode 100644 lib/rhashtable.c
--
1.9.3
next reply other threads:[~2014-07-29 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 11:41 Thomas Graf [this message]
2014-07-29 11:41 ` [PATCH 1/2] lib: Resizable, Scalable, Concurrent Hash Table Thomas Graf
2014-07-29 15:30 ` Josh Triplett
2014-07-29 16:55 ` Thomas Graf
2014-07-29 11:41 ` [PATCH 2/2] netlink: Convert netlink_lookup() to use RCU protected hash table Thomas Graf
2014-07-29 15:58 ` Tobias Klauser
2014-07-29 16:34 ` Thomas Graf
2014-07-31 2:08 ` [PATCH 0/2 net-next] Lockless netlink_lookup() with new concurrent " David Miller
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=cover.1406633945.git.tgraf@suug.ch \
--to=tgraf@suug.ch \
--cc=challa@noironetworks.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=josh@joshtriplett.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=walpole@cs.pdx.edu \
/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
Powered by JetHome