From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com,
hideaki@yoshifuji.org, vyasevich@gmail.com,
nicolas.dichtel@6wind.com, kafai@fb.com
Subject: Re: [PATCH net] ipv6: remove rt6i_genid
Date: Mon, 29 Sep 2014 16:51:46 -0400 (EDT) [thread overview]
Message-ID: <20140929.165146.886742875592532179.davem@davemloft.net> (raw)
In-Reply-To: <7e1b4e2dbe855fa461a4e87e0482ac16b6982c2f.1411857958.git.hannes@stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Sun, 28 Sep 2014 00:46:06 +0200
> Eric Dumazet noticed that all no-nonexthop or no-gateway routes which
> are already marked DST_HOST (e.g. input routes routes) will always be
> invalidated during sk_dst_check. Thus per-socket dst caching absolutely
> had no effect and early demuxing had no effect.
>
> Thus this patch removes rt6i_genid: fn_sernum already gets modified during
> add operations, so we only must ensure we mutate fn_sernum during ipv6
> address remove operations. This is a fairly cost extensive operations,
> but address removal should not happen that often. Also our mtu update
> functions do the same and we heard no complains so far. xfrm policy
> changes also cause a call into fib6_flush_trees. Also plug a hole in
> rt6_info (no cacheline changes).
>
> I verified via tracing that this change has effect.
>
> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Ok, I'll apply this because it does correctly and simply fix the
problem now, thanks.
I'll also queue it up for -stable.
However, longer-term:
> static inline void rt_genid_bump_ipv6(struct net *net)
> {
> + if (__fib6_flush_trees)
> + __fib6_flush_trees(net);
> }
I'd really like to see this go away.
prev parent reply other threads:[~2014-09-29 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 22:46 [PATCH net] ipv6: remove rt6i_genid Hannes Frederic Sowa
2014-09-29 20:51 ` 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=20140929.165146.886742875592532179.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=hideaki@yoshifuji.org \
--cc=kafai@fb.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