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, shuah@kernel.org, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 00/11] mlxsw: Support for nexthop group statistics
Date: Mon, 11 Mar 2024 22:00:34 +0000 [thread overview]
Message-ID: <171019443441.9697.6658731872868510841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1709901020.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 8 Mar 2024 13:59:44 +0100 you wrote:
> ECMP is a fundamental component in L3 designs. However, it's fragile. Many
> factors influence whether an ECMP group will operate as intended: hash
> policy (i.e. the set of fields that contribute to ECMP hash calculation),
> neighbor validity, hash seed (which might lead to polarization) or the type
> of ECMP group used (hash-threshold or resilient).
>
> At the same time, collection of statistics that would help an operator
> determine that the group performs as desired, is difficult.
>
> [...]
Here is the summary with links:
- [net-next,01/11] net: nexthop: Initialize NH group ID in resilient NH group notifiers
https://git.kernel.org/netdev/net-next/c/2d32c49386cb
- [net-next,02/11] net: nexthop: Have all NH notifiers carry NH ID
https://git.kernel.org/netdev/net-next/c/e99eb57e9b14
- [net-next,03/11] mlxsw: spectrum_router: Rename two functions
https://git.kernel.org/netdev/net-next/c/64f962c65fe3
- [net-next,04/11] mlxsw: spectrum_router: Have mlxsw_sp_nexthop_counter_enable() return int
https://git.kernel.org/netdev/net-next/c/8acb480e43c8
- [net-next,05/11] mlxsw: spectrum: Allow fetch-and-clear of flow counters
https://git.kernel.org/netdev/net-next/c/6fb88aaf272a
- [net-next,06/11] mlxsw: spectrum_router: Avoid allocating NH counters twice
https://git.kernel.org/netdev/net-next/c/79fa52145e19
- [net-next,07/11] mlxsw: spectrum_router: Add helpers for nexthop counters
https://git.kernel.org/netdev/net-next/c/10bf92fd775e
- [net-next,08/11] mlxsw: spectrum_router: Track NH ID's of group members
https://git.kernel.org/netdev/net-next/c/41acb5549e60
- [net-next,09/11] mlxsw: spectrum_router: Support nexthop group hardware statistics
https://git.kernel.org/netdev/net-next/c/5a5a98e5176e
- [net-next,10/11] mlxsw: spectrum_router: Share nexthop counters in resilient groups
https://git.kernel.org/netdev/net-next/c/44c2fbebe18a
- [net-next,11/11] selftests: forwarding: Add a test for NH group stats
https://git.kernel.org/netdev/net-next/c/a22b042660ca
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-03-11 22:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 12:59 [PATCH net-next 00/11] mlxsw: Support for nexthop group statistics Petr Machata
2024-03-08 12:59 ` [PATCH net-next 01/11] net: nexthop: Initialize NH group ID in resilient NH group notifiers Petr Machata
2024-03-08 12:59 ` [PATCH net-next 02/11] net: nexthop: Have all NH notifiers carry NH ID Petr Machata
2024-03-08 12:59 ` [PATCH net-next 03/11] mlxsw: spectrum_router: Rename two functions Petr Machata
2024-03-08 12:59 ` [PATCH net-next 04/11] mlxsw: spectrum_router: Have mlxsw_sp_nexthop_counter_enable() return int Petr Machata
2024-03-08 12:59 ` [PATCH net-next 05/11] mlxsw: spectrum: Allow fetch-and-clear of flow counters Petr Machata
2024-03-08 12:59 ` [PATCH net-next 06/11] mlxsw: spectrum_router: Avoid allocating NH counters twice Petr Machata
2024-03-08 12:59 ` [PATCH net-next 07/11] mlxsw: spectrum_router: Add helpers for nexthop counters Petr Machata
2024-03-08 12:59 ` [PATCH net-next 08/11] mlxsw: spectrum_router: Track NH ID's of group members Petr Machata
2024-03-08 12:59 ` [PATCH net-next 09/11] mlxsw: spectrum_router: Support nexthop group hardware statistics Petr Machata
2024-03-08 12:59 ` [PATCH net-next 10/11] mlxsw: spectrum_router: Share nexthop counters in resilient groups Petr Machata
2024-03-08 12:59 ` [PATCH net-next 11/11] selftests: forwarding: Add a test for NH group stats Petr Machata
2024-03-08 17:03 ` Jakub Kicinski
2024-03-08 22:31 ` Petr Machata
2024-03-09 3:48 ` Jakub Kicinski
2024-03-09 4:47 ` David Ahern
2024-03-11 10:59 ` Petr Machata
2024-03-11 11:00 ` Petr Machata
2024-03-11 15:59 ` Jakub Kicinski
2024-03-11 16:30 ` Petr Machata
2024-03-11 17:52 ` Jakub Kicinski
2024-03-11 22: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=171019443441.9697.6658731872868510841.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--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=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.