From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH net-next-2.6] ipv6: mcast: RCU conversions
Date: Wed, 09 Jun 2010 18:07:37 -0700 (PDT) [thread overview]
Message-ID: <20100609.180737.48514741.davem@davemloft.net> (raw)
In-Reply-To: <1275980702.2775.193.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 08 Jun 2010 09:05:02 +0200
> - ipv6_sock_mc_join() : doesnt touch dev refcount
>
> - ipv6_sock_mc_drop() : doesnt touch dev/idev refcounts
>
> - ip6_mc_find_dev() becomes ip6_mc_find_dev_rcu() (called from rcu),
> and doesnt touch dev/idev refcounts
>
> - ipv6_sock_mc_close() : doesnt touch dev/idev refcounts
>
> - ip6_mc_source() uses ip6_mc_find_dev_rcu()
>
> - ip6_mc_msfilter() uses ip6_mc_find_dev_rcu()
>
> - ip6_mc_msfget() uses ip6_mc_find_dev_rcu()
>
> - ipv6_dev_mc_dec(), ipv6_chk_mcast_addr(),
> igmp6_event_query(), igmp6_event_report(),
> mld_sendpack(), igmp6_send() dont touch idev refcount
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Applied.
prev parent reply other threads:[~2010-06-10 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 7:05 [PATCH net-next-2.6] ipv6: mcast: RCU conversions Eric Dumazet
2010-06-10 1:07 ` David Miller [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=20100609.180737.48514741.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).