From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Cypher Wu <cypher.w@gmail.com>,
linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next-2.6] igmp: RCU conversion of in_dev->mc_list
Date: Fri, 12 Nov 2010 15:26:14 +0100 [thread overview]
Message-ID: <1289571974.3185.254.camel@edumazet-laptop> (raw)
In-Reply-To: <1289568858.3185.252.camel@edumazet-laptop>
Le vendredi 12 novembre 2010 à 14:34 +0100, Eric Dumazet a écrit :
> Le vendredi 12 novembre 2010 à 10:22 +0100, Eric Dumazet a écrit :
> > Le vendredi 12 novembre 2010 à 16:19 +0800, Américo Wang a écrit :
> > > On Fri, Nov 12, 2010 at 08:27:54AM +0100, Eric Dumazet wrote:
> >
> > > >A RCU conversion is far more complex.
> > > >
> > >
> > > Yup.
> >
> >
> > Well, actually this is easy in this case.
> >
> > I'll post a patch to do this RCU conversion.
> >
> >
>
> Note : compile tested only, I'll appreciate if someone can test it ;)
>
> Note: one patch from net-2.6 is not yet included in net-next-2.6, so
> please make sure you have it before testing ;)
>
> ( http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commitdiff;h=18943d292facbc70e6a36fc62399ae833f64671b )
>
>
> Thanks
>
> [PATCH net-next-2.6] igmp: RCU conversion of in_dev->mc_list
>
> in_dev->mc_list is protected by one rwlock (in_dev->mc_list_lock).
>
> This can easily be converted to a RCU protection.
>
> Writers hold RTNL, so mc_list_lock is removed, not replaced by a
> spinlock.
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> Cc: Cypher Wu <cypher.w@gmail.com>
> Cc: Américo Wang <xiyou.wangcong@gmail.com>
> ---
...
> void ip_mc_up(struct in_device *in_dev)
> {
> - struct ip_mc_list *i;
> + struct ip_mc_list *pmc;
>
> ASSERT_RTNL();
>
> ip_mc_inc_group(in_dev, IGMP_ALL_HOSTS);
>
> - for (i=in_dev->mc_list; i; i=i->next)
> - igmp_group_added(i);
> + for_each_pmc_rtnl(in_dev, pmc);
> + igmp_group_added(pmc);
> }
Oops there is an extra ; after the for_each_pmc_rtnl(in_dev, pmc)
should be
for_each_pmc_rtnl(in_dev, pmc)
igmp_group_added(pmc);
next prev parent reply other threads:[~2010-11-12 14:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikvT=x9eBovn2-m6HLqk7wyXSAR3sc9jCQ0C6mL@mail.gmail.com>
2010-11-11 15:23 ` Kernel rwlock design, Multicore and IGMP Eric Dumazet
2010-11-11 15:32 ` Eric Dumazet
2010-11-12 3:32 ` Cypher Wu
2010-11-12 6:28 ` Américo Wang
2010-11-12 7:13 ` Américo Wang
2010-11-12 7:27 ` Eric Dumazet
2010-11-12 8:19 ` Américo Wang
2010-11-12 9:09 ` Yong Zhang
2010-11-12 9:18 ` Américo Wang
2010-11-12 11:06 ` Cypher Wu
2010-11-13 6:35 ` Américo Wang
2010-11-12 13:00 ` Yong Zhang
2010-11-13 6:28 ` Américo Wang
2010-11-12 9:22 ` Eric Dumazet
2010-11-12 9:33 ` Américo Wang
2010-11-12 13:34 ` [PATCH net-next-2.6] igmp: RCU conversion of in_dev->mc_list Eric Dumazet
2010-11-12 14:26 ` Eric Dumazet [this message]
2010-11-12 15:46 ` [PATCH net-next-2.6 V2] " Eric Dumazet
2010-11-12 21:19 ` David Miller
2010-11-13 6:44 ` Américo Wang
2010-11-13 22:54 ` Kernel rwlock design, Multicore and IGMP Peter Zijlstra
2010-11-12 11:10 ` Cypher Wu
2010-11-12 11:25 ` Eric Dumazet
2010-11-13 22:53 ` Peter Zijlstra
[not found] ` <ZXmP8hjgLHA.4648@exchange1.tad.internal.tilera.com>
2010-11-13 23:03 ` Chris Metcalf
2010-11-15 7:22 ` Cypher Wu
2010-11-15 11:18 ` Cypher Wu
2010-11-15 11:31 ` Eric Dumazet
2010-11-17 1:30 ` Cypher Wu
2010-11-17 4:43 ` Eric Dumazet
2010-11-15 14:18 ` [PATCH] arch/tile: fix rwlock so would-be write lockers don't block new readers Chris Metcalf
2010-11-15 14:52 ` Eric Dumazet
2010-11-15 15:10 ` Chris Metcalf
2010-11-22 5:39 ` Cypher Wu
2010-11-22 13:35 ` Chris Metcalf
2010-11-23 1:36 ` Cypher Wu
2010-11-23 21:02 ` Chris Metcalf
2010-11-24 2:53 ` Cypher Wu
2010-11-24 14:09 ` Chris Metcalf
2010-11-24 16:37 ` Cypher Wu
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=1289571974.3185.254.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=cypher.w@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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