From: Florian Westphal <fw@strlen.de>
To: <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/2] ipv6: addrconf: make two more doit functions not use rtnl mutex
Date: Wed, 11 Oct 2017 10:27:59 +0200 [thread overview]
Message-ID: <20171011082801.12715-1-fw@strlen.de> (raw)
ipv6 RTM_GETNETCONF and RTM_GETADDR don't seem to require strict
serialization via rtnl mutex, so switch both to DOIT_UNLOCKED and increment
device reference counts instead.
Alternative would be to use rcu which would need some minor
code re-arrangements (we can't use GFP_ATOMIC for buffer allocation in that
case).
addrconf.c | 38 +++++++++++++++++++++-----------------
1 file changed, 21 insertions(+), 17 deletions(-)
next reply other threads:[~2017-10-11 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 8:27 Florian Westphal [this message]
2017-10-11 8:28 ` [PATCH net-next 1/2] ipv6: addrconf: don't use rtnl mutex in RTM_GETNETCONF Florian Westphal
2017-10-12 3:17 ` David Miller
2017-10-11 8:28 ` [PATCH net-next 2/2] ipv6: addrconf: don't use rtnl mutex in RTM_GETADDR Florian Westphal
2017-10-12 3:17 ` 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=20171011082801.12715-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
/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).