From: patchwork-bot+netdevbpf@kernel.org
To: Oz Shlomo <ozsh@nvidia.com>
Cc: netdev@vger.kernel.org, saeedm@nvidia.com, roid@nvidia.com,
jiri@nvidia.com, mleitner@redhat.com, simon.horman@corigine.com,
baowen.zheng@corigine.com, jhs@mojatatu.com,
ecree.xilinx@gmail.com, kuba@kernel.org
Subject: Re: [PATCH net-next v4 0/9] add support for per action hw stats
Date: Tue, 14 Feb 2023 10:20:19 +0000 [thread overview]
Message-ID: <167637001900.27531.17888495360173690530.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230212132520.12571-1-ozsh@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 12 Feb 2023 15:25:11 +0200 you wrote:
> There are currently two mechanisms for populating hardware stats:
> 1. Using flow_offload api to query the flow's statistics.
> The api assumes that the same stats values apply to all
> the flow's actions.
> This assumption breaks when action drops or jumps over following
> actions.
> 2. Using hw_action api to query specific action stats via a driver
> callback method. This api assures the correct action stats for
> the offloaded action, however, it does not apply to the rest of the
> actions in the flow's actions array, as elaborated below.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/9] net/sched: optimize action stats api calls
https://git.kernel.org/netdev/net-next/c/8f2ca70c07f4
- [net-next,v4,2/9] net/sched: act_pedit, setup offload action for action stats query
https://git.kernel.org/netdev/net-next/c/3320f36fd8ad
- [net-next,v4,3/9] net/sched: pass flow_stats instead of multiple stats args
https://git.kernel.org/netdev/net-next/c/ac7d27907d54
- [net-next,v4,4/9] net/sched: introduce flow_offload action cookie
https://git.kernel.org/netdev/net-next/c/d307b2c6f962
- [net-next,v4,5/9] net/sched: support per action hw stats
https://git.kernel.org/netdev/net-next/c/5246c896b805
- [net-next,v4,6/9] net/mlx5e: TC, add hw counter to branching actions
https://git.kernel.org/netdev/net-next/c/e9d1061d8727
- [net-next,v4,7/9] net/mlx5e: TC, store tc action cookies per attr
https://git.kernel.org/netdev/net-next/c/cca7eac13856
- [net-next,v4,8/9] net/mlx5e: TC, map tc action cookie to a hw counter
https://git.kernel.org/netdev/net-next/c/d13674b1d14c
- [net-next,v4,9/9] net/mlx5e: TC, support per action stats
https://git.kernel.org/netdev/net-next/c/2b68d659a704
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:[~2023-02-14 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 13:25 [PATCH net-next v4 0/9] add support for per action hw stats Oz Shlomo
2023-02-12 13:25 ` [PATCH net-next v4 1/9] net/sched: optimize action stats api calls Oz Shlomo
2023-02-12 14:58 ` Jamal Hadi Salim
2023-02-12 13:25 ` [PATCH net-next v4 2/9] net/sched: act_pedit, setup offload action for action stats query Oz Shlomo
2023-02-12 14:59 ` Jamal Hadi Salim
2023-02-12 13:25 ` [PATCH net-next v4 3/9] net/sched: pass flow_stats instead of multiple stats args Oz Shlomo
2023-02-12 15:01 ` Jamal Hadi Salim
2023-02-12 13:25 ` [PATCH net-next v4 4/9] net/sched: introduce flow_offload action cookie Oz Shlomo
2023-02-12 15:14 ` Jamal Hadi Salim
2023-02-12 13:25 ` [PATCH net-next v4 5/9] net/sched: support per action hw stats Oz Shlomo
2023-02-12 15:12 ` Jamal Hadi Salim
2023-02-12 13:25 ` [PATCH net-next v4 6/9] net/mlx5e: TC, add hw counter to branching actions Oz Shlomo
2023-02-12 13:25 ` [PATCH net-next v4 7/9] net/mlx5e: TC, store tc action cookies per attr Oz Shlomo
2023-02-12 13:25 ` [PATCH net-next v4 8/9] net/mlx5e: TC, map tc action cookie to a hw counter Oz Shlomo
2023-02-12 13:25 ` [PATCH net-next v4 9/9] net/mlx5e: TC, support per action stats Oz Shlomo
2023-02-14 10:20 ` 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=167637001900.27531.17888495360173690530.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=baowen.zheng@corigine.com \
--cc=ecree.xilinx@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.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 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.