From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, idosch@nvidia.com,
dsahern@kernel.org, sharpd@nvidia.com, horms@kernel.org,
przemyslaw.kitszel@intel.com, mlxsw@nvidia.com
Subject: Re: [PATCH net-next v2 0/6] net: nexthop: Increase weight to u16
Date: Tue, 13 Aug 2024 01:00:33 +0000 [thread overview]
Message-ID: <172351083351.1180801.8605860552440119209.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1723036486.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 Aug 2024 16:13:45 +0200 you wrote:
> In CLOS networks, as link failures occur at various points in the network,
> ECMP weights of the involved nodes are adjusted to compensate. With high
> fan-out of the involved nodes, and overall high number of nodes,
> a (non-)ECMP weight ratio that we would like to configure does not fit into
> 8 bits. Instead of, say, 255:254, we might like to configure something like
> 1000:999. For these deployments, the 8-bit weight may not be enough.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/6] net: nexthop: Add flag to assert that NHGRP reserved fields are zero
https://git.kernel.org/netdev/net-next/c/75bab45e6b2d
- [net-next,v2,2/6] net: nexthop: Increase weight to u16
https://git.kernel.org/netdev/net-next/c/b72a6a7ab957
- [net-next,v2,3/6] selftests: router_mpath: Sleep after MZ
https://git.kernel.org/netdev/net-next/c/110d3ffe9d2b
- [net-next,v2,4/6] selftests: router_mpath_nh: Test 16-bit next hop weights
https://git.kernel.org/netdev/net-next/c/bb89fdacf99c
- [net-next,v2,5/6] selftests: router_mpath_nh_res: Test 16-bit next hop weights
https://git.kernel.org/netdev/net-next/c/dce0765c1d5b
- [net-next,v2,6/6] selftests: fib_nexthops: Test 16-bit next hop weights
https://git.kernel.org/netdev/net-next/c/4b808f447332
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-08-13 1:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 14:13 [PATCH net-next v2 0/6] net: nexthop: Increase weight to u16 Petr Machata
2024-08-07 14:13 ` [PATCH net-next v2 1/6] net: nexthop: Add flag to assert that NHGRP reserved fields are zero Petr Machata
2024-08-08 7:13 ` Ido Schimmel
2024-08-07 14:13 ` [PATCH net-next v2 2/6] net: nexthop: Increase weight to u16 Petr Machata
2024-08-07 14:13 ` [PATCH net-next v2 3/6] selftests: router_mpath: Sleep after MZ Petr Machata
2024-08-07 14:13 ` [PATCH net-next v2 4/6] selftests: router_mpath_nh: Test 16-bit next hop weights Petr Machata
2024-08-07 14:13 ` [PATCH net-next v2 5/6] selftests: router_mpath_nh_res: " Petr Machata
2024-08-07 14:13 ` [PATCH net-next v2 6/6] selftests: fib_nexthops: " Petr Machata
2024-08-08 13:28 ` [PATCH net-next v2 0/6] net: nexthop: Increase weight to u16 Jakub Kicinski
2024-08-09 9:48 ` Petr Machata
2024-08-10 4:09 ` Jakub Kicinski
2024-08-12 10:09 ` Petr Machata
2024-08-13 1:00 ` patchwork-bot+netdevbpf [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=172351083351.1180801.8605860552440119209.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sharpd@nvidia.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).