From: Eric Dumazet <eric.dumazet@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: Does rtnl_lock inhibit incoming traffic?
Date: Wed, 29 May 2013 13:21:20 -0700 [thread overview]
Message-ID: <1369858880.5109.82.camel@edumazet-glaptop> (raw)
In-Reply-To: <51A6522D.2000008@hartkopp.net>
On Wed, 2013-05-29 at 21:08 +0200, Oliver Hartkopp wrote:
> Hello,
>
> AFAIK the rtnl_lock is used (at least) to protect the configuration of
> netdevices and routing tables.
>
> Is the reception of incoming traffic inhibited while the rtnl_lock is set, or
> would i need to protect the data structures to be modified with an additional
> spinlock_bh() / write_lock_bh()?
>
> Like this one here:
>
> http://lxr.linux.no/#linux+v3.9.4/net/ipv6/ip6mr.c#L1573
Reception of incoming traffic is not inhibited by rtnl.
And spinlock_bh()/write_lock_bh() only disable current cpu from
receiving frames, but other cpus can still handle incoming traffic.
prev parent reply other threads:[~2013-05-29 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 19:08 Does rtnl_lock inhibit incoming traffic? Oliver Hartkopp
2013-05-29 20:21 ` Eric Dumazet [this message]
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=1369858880.5109.82.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.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