From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Vlad Yasevich <vyasevich@gmail.com>
Cc: netdev@vger.kernel.org, Eric Dumazet <eric.dumazet@gmail.com>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [PATCH net-next] ipv6: implement rt_genid_bump_ipv6 with fn_sernum and remove rt6i_genid
Date: Wed, 10 Sep 2014 15:42:17 +0200 [thread overview]
Message-ID: <1410356537.3135.21.camel@localhost> (raw)
In-Reply-To: <54105185.7010206@gmail.com>
Hi Vlad,
On Mi, 2014-09-10 at 09:26 -0400, Vlad Yasevich wrote:
> On 09/10/2014 05:31 AM, Hannes Frederic Sowa wrote:
> > Some special routes will never be cloned in IPv6. Those are mainly
> > DST_HOST routes without RTF_NONEXTHOP or RTF_GATEWAY flags, thus mostly
> > routes handling the input path.
> >
> > rt_genid depends on rt6_info clones being removed from the trie and
> > recreated with current rt6i_genid, thus bumping the genid would invalidate
> > all routes cached in the sockets and relookup will recreate them. But in
> > case a non-cloned route ends up in the per-socket cache, it will never
> > be recreated, thus will never get a current rt_genid.
> >
> > After the rt_genid is incremented for the first time all those routes
> > will always get invalidated by ip6_dst_check on the next check, thus
> > making early socket demultiplexing absolutely pointless for IPv6. It is
> > not possible to solve this with rt6i_genid, thus remove it.
> >
> > In case we need to force the sockets to relookup the routes we now
> > increase the fn_sernum on all fibnodes in the routing tree. This is a
> > costly operation but should only happen if we have major routing/policy
> > changes in the kernel (e.g. manual route adding/removal, xfrm policy
> > changes). Also this patch optimized the walk over the trie a bit, we
> > don't touch every rt6_info but only touch the fib6_nodes.
> >
> > Thanks to Eric Dumazet who noticed this problem.
>
> I also noticed the ipv6_ifa_notify() is called a lot with even being
> 0. This will only trigger rtnl notification, but would not trigger any
> routing table changes, but would trigger a call to bump the gen_id
> which now would perform a rather expensive clean-table operation.
>
> In particular the loop in manage_tempaddrs() is very scary as it can
> bump the rev multiples times.
>
> I think it the genid bump in __ipv6_ifa_notify() should only happen
> if there was an actual address change.
Yes, maybe we don't even need to bump id in ipv6_ifa_notify at all, I am
still investigating. :)
Thanks,
Hannes
next prev parent reply other threads:[~2014-09-10 13:42 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 18:19 Performance regression on kernels 3.10 and newer Alexander Duyck
2014-08-14 18:46 ` Eric Dumazet
2014-08-14 19:50 ` Eric Dumazet
2014-08-14 19:59 ` Rick Jones
2014-08-14 20:31 ` Alexander Duyck
2014-08-14 20:51 ` Eric Dumazet
2014-08-14 20:46 ` Eric Dumazet
2014-08-14 23:16 ` Alexander Duyck
2014-08-14 23:20 ` David Miller
2014-08-14 23:25 ` Tom Herbert
2014-08-21 23:24 ` David Miller
2014-09-06 14:45 ` Eric Dumazet
2014-09-06 15:27 ` Eric Dumazet
2014-09-06 15:46 ` Eric Dumazet
2014-09-06 16:38 ` Eric Dumazet
2014-09-06 18:21 ` Eric Dumazet
2014-09-07 19:05 ` [PATCH net] ipv6: refresh rt6i_genid in ip6_pol_route() Eric Dumazet
2014-09-07 22:54 ` David Miller
2014-09-08 4:18 ` Eric Dumazet
2014-09-08 4:27 ` David Miller
2014-09-08 4:43 ` Eric Dumazet
2014-09-08 4:59 ` David Miller
2014-09-08 5:07 ` Eric Dumazet
2014-09-08 8:11 ` Nicolas Dichtel
2014-09-08 10:28 ` Eric Dumazet
2014-09-08 12:16 ` Nicolas Dichtel
2014-09-08 18:48 ` Vlad Yasevich
2014-09-09 12:58 ` Hannes Frederic Sowa
2014-09-10 9:31 ` [PATCH net-next] ipv6: implement rt_genid_bump_ipv6 with fn_sernum and remove rt6i_genid Hannes Frederic Sowa
2014-09-10 13:26 ` Vlad Yasevich
2014-09-10 13:42 ` Hannes Frederic Sowa [this message]
2014-09-10 20:09 ` David Miller
2014-09-11 8:30 ` Hannes Frederic Sowa
2014-09-11 12:22 ` Vlad Yasevich
2014-09-11 12:40 ` Hannes Frederic Sowa
2014-09-11 12:05 ` Hannes Frederic Sowa
2014-09-11 14:19 ` Vlad Yasevich
2014-09-11 14:32 ` Hannes Frederic Sowa
2014-09-11 14:44 ` Vlad Yasevich
2014-09-11 14:47 ` Hannes Frederic Sowa
2014-09-08 15:06 ` [PATCH v2 net-next] tcp: remove dst refcount false sharing for prequeue mode Eric Dumazet
2014-09-08 21:21 ` David Miller
2014-09-08 21:30 ` Eric Dumazet
2014-09-08 22:41 ` David Miller
2014-09-09 23:56 ` David Miller
2014-08-15 17:15 ` Performance regression on kernels 3.10 and newer Alexander Duyck
2014-08-15 17:59 ` Eric Dumazet
2014-08-15 18:49 ` Tom Herbert
2014-08-15 19:10 ` Alexander Duyck
2014-08-15 22:16 ` Tom Herbert
2014-08-15 23:23 ` Alexander Duyck
2014-08-18 9:03 ` David Laight
2014-08-18 15:22 ` Alexander Duyck
2014-08-18 15:29 ` Rick Jones
2014-08-21 23:51 ` David Miller
2014-08-14 23:48 ` Eric Dumazet
2014-08-15 0:33 ` Rick Jones
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=1410356537.3135.21.camel@localhost \
--to=hannes@stressinduktion.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=vyasevich@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;
as well as URLs for NNTP newsgroup(s).