From: Pavel Balaev <balaevpa@infotecs.ru>
To: <netdev@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>, Shuah Khan <shuah@kernel.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH v5 net-next 0/3] net: multipath routing: configurable seed
Date: Tue, 27 Apr 2021 18:33:54 +0300 [thread overview]
Message-ID: <YIgu4hLNSa69/oFZ@rnd> (raw)
This is the fifth version of the mpath seed series.
This patch series adds ability for a user to assign seed value
to multipath route hashes.
changes v4:
- patch was splited to patch series
- remove CONFIG_IP_ROUTE_MULTIPATH define from flow_multipath_hash_from_keys(),
it used in both IPv4/IPv6 protos.
The mainlining discussion history of this branch:
v4: https://lore.kernel.org/netdev/21a2fb1925b215cc48ab8e2f783a7de7@void.so
Balaev Pavel (3):
net/ipv4: multipath routing: configurable seed
net/ipv6: multipath routing: configurable seed
selftests/net/forwarding: configurable seed tests
Documentation/networking/ip-sysctl.rst | 14 +
include/net/flow_dissector.h | 2 +
include/net/netns/ipv4.h | 2 +
include/net/netns/ipv6.h | 3 +
net/core/flow_dissector.c | 7 +
net/ipv4/route.c | 10 +-
net/ipv4/sysctl_net_ipv4.c | 97 ++++++
net/ipv6/route.c | 10 +-
net/ipv6/sysctl_net_ipv6.c | 96 ++++++
tools/testing/selftests/net/forwarding/Makefile | 1 +
tools/testing/selftests/net/forwarding/lib.sh | 28 ++
.../net/forwarding/router_mpath_seed.sh (new +x) | 347 +++++++++++++++++++++
12 files changed, 615 insertions(+), 2 deletions(-)
reply other threads:[~2021-04-27 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YIgu4hLNSa69/oFZ@rnd \
--to=balaevpa@infotecs.ru \
--cc=christophe.jaillet@wanadoo.fr \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@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).