From: Ying Xue <ying.xue@windriver.com>
To: <tgraf@suug.ch>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/3] remove nl_sk_hash_lock from netlink socket
Date: Fri, 9 Jan 2015 16:23:35 +0800 [thread overview]
Message-ID: <1420791818-22150-1-git-send-email-ying.xue@windriver.com> (raw)
After tipc socket successfully avoids the involvement of an extra lock
with rhashtable_lookup_insert(), it's possible for netlink socket to
remove its hash socket lock now. But as netlink socket needs a compare
function to look for an object, we first introduce a new function
called rhashtable_lookup_compare_insert() in commit #1 which is
implemented based on original rhashtable_lookup_insert(). We
subsequently remove nl_sk_hash_lock from netlink socket with the new
introduced function in commit #2. Lastly, as Thomas requested, we add
commit #3 to indicate the implementation of what the grow and shrink
decision function must enforce min/max shift.
Ying Xue (3):
rhashtable: involve rhashtable_lookup_compare_insert routine
netlink: eliminate nl_sk_hash_lock
rhashtable: add a note for grow and shrink decision functions
include/linux/rhashtable.h | 9 +++++++++
lib/rhashtable.c | 42 ++++++++++++++++++++++++++++++++++++++++--
net/netlink/af_netlink.c | 43 ++++++++++++++++++++++---------------------
net/netlink/af_netlink.h | 1 -
net/netlink/diag.c | 10 +++++-----
5 files changed, 76 insertions(+), 29 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-01-09 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 8:23 Ying Xue [this message]
2015-01-09 8:23 ` [PATCH net-next 1/3] rhashtable: involve rhashtable_lookup_compare_insert routine Ying Xue
2015-01-09 10:31 ` Thomas Graf
2015-01-09 8:23 ` [PATCH net-next 2/3] netlink: eliminate nl_sk_hash_lock Ying Xue
2015-01-09 10:55 ` Thomas Graf
2015-01-12 21:27 ` David Miller
2015-01-09 8:23 ` [PATCH net-next 3/3] rhashtable: add a note for grow and shrink decision functions Ying Xue
2015-01-09 10:31 ` Thomas Graf
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=1420791818-22150-1-git-send-email-ying.xue@windriver.com \
--to=ying.xue@windriver.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).