From: Jakub Kicinski <kuba@kernel.org>
To: Oz Shlomo <ozsh@nvidia.com>
Cc: netdev@vger.kernel.org, Jiri Pirko <jiri@nvidia.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Simon Horman <simon.horman@corigine.com>,
Baowen Zheng <baowen.zheng@corigine.com>,
Vlad Buslov <vladbu@nvidia.com>, Ido Schimmel <idosch@nvidia.com>,
Roi Dayan <roid@nvidia.com>
Subject: Re: [ RFC net-next 0/3] net: flow_offload: add support for per action hw stats
Date: Wed, 17 Aug 2022 09:02:37 -0700 [thread overview]
Message-ID: <20220817090237.79e42eb3@kernel.org> (raw)
In-Reply-To: <a2b5d395-01c7-4ca4-a844-2ba6952ac66b@nvidia.com>
On Wed, 17 Aug 2022 17:46:54 +0300 Oz Shlomo wrote:
> On 8/16/2022 9:19 PM, Jakub Kicinski wrote:
> > On Tue, 16 Aug 2022 12:23:35 +0300 Oz Shlomo wrote:
> >> This series provides the platform to query per action stats for in_hw flows.
> >
> > I'd like to make sure we document the driver-facing APIs going forward,
> > please consider adding a doc.
>
> Is there an existing document that we can update?
Not that I know of.
prev parent reply other threads:[~2022-08-17 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 9:23 [ RFC net-next 0/3] net: flow_offload: add support for per action hw stats Oz Shlomo
2022-08-16 9:23 ` [ RFC net-next 1/3] net: sched: Pass flow_stats instead of multiple stats args Oz Shlomo
2022-08-16 9:23 ` [ RFC net-next 2/3] net: flow_offload: add action stats api Oz Shlomo
2022-08-16 13:42 ` Edward Cree
2022-08-17 14:43 ` Oz Shlomo
2022-09-28 15:19 ` Oz Shlomo
2022-08-16 9:23 ` [ RFC net-next 3/3] net/sched: act_api: update hw stats for tc action list Oz Shlomo
2022-08-16 18:19 ` [ RFC net-next 0/3] net: flow_offload: add support for per action hw stats Jakub Kicinski
2022-08-17 14:46 ` Oz Shlomo
2022-08-17 16:02 ` Jakub Kicinski [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=20220817090237.79e42eb3@kernel.org \
--to=kuba@kernel.org \
--cc=baowen.zheng@corigine.com \
--cc=idosch@nvidia.com \
--cc=jhs@mojatatu.com \
--cc=jiri@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=roid@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=vladbu@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).