From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: netdev@vger.kernel.org
Cc: hideaki@yoshifuji.org, kafai@fb.com
Subject: [PATCH net-next 0/5] ipv6: cleanup after rt6_genid removal
Date: Mon, 6 Oct 2014 10:52:09 +0200 [thread overview]
Message-ID: <cover.1412585162.git.hannes@stressinduktion.org> (raw)
Leftover patches after rt6_genid removal after 705f1c869d577c ("ipv6:
remove rt6i_genid").
Major two changes are:
* keep fib6_sernum per namespace to reduce number of flushes in case
system has high number of namespaces
* make fn_sernum updates cheaper
Hannes Frederic Sowa (5):
ipv6: minor fib6 cleanups like type safety, bool conversion, inline
removal
ipv6: make rt_sernum atomic and serial number fields ordinary ints
ipv6: only generate one new serial number per fib mutation
ipv6: make fib6 serial number per namespace
ipv6: don't walk node's leaf during serial number update
include/net/ip6_fib.h | 16 +++++--
include/net/netns/ipv6.h | 2 +-
net/ipv6/af_inet6.c | 2 +-
net/ipv6/ip6_fib.c | 106 +++++++++++++++++++++++++----------------------
4 files changed, 71 insertions(+), 55 deletions(-)
--
1.9.3
next reply other threads:[~2014-10-06 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 8:52 Hannes Frederic Sowa [this message]
2014-10-06 8:52 ` [PATCH net-next 1/5] ipv6: minor fib6 cleanups like type safety, bool conversion, inline removal Hannes Frederic Sowa
2014-10-06 17:23 ` Cong Wang
2014-10-06 8:52 ` [PATCH net-next 2/5] ipv6: make rt_sernum atomic and serial number fields ordinary ints Hannes Frederic Sowa
2014-10-06 17:26 ` Cong Wang
2014-10-06 8:52 ` [PATCH net-next 3/5] ipv6: only generate one new serial number per fib mutation Hannes Frederic Sowa
2014-10-06 8:52 ` [PATCH net-next 4/5] ipv6: make fib6 serial number per namespace Hannes Frederic Sowa
2014-10-06 8:52 ` [PATCH net-next 5/5] ipv6: don't walk node's leaf during serial number update Hannes Frederic Sowa
2014-10-06 17:58 ` Cong Wang
2014-10-06 18:02 ` Hannes Frederic Sowa
2014-10-06 18:27 ` Cong Wang
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=cover.1412585162.git.hannes@stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=hideaki@yoshifuji.org \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.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).