From: Edward Cree <ecree@solarflare.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
netdev <netdev@vger.kernel.org>, "Jiri Pirko" <jiri@resnulli.us>,
Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: TC stats / hw offload question
Date: Thu, 25 Apr 2019 14:23:08 +0100 [thread overview]
Message-ID: <58c74d0f-b92e-31f9-9828-24fb04129534@solarflare.com> (raw)
In-Reply-To: <26afcaaf-abdf-42ad-1715-5af9c6f3c2ef@solarflare.com>
On 24/04/2019 16:03, Edward Cree wrote:
> static int efx_tc_flower_replace(struct efx_nic *efx,
> struct net_device *net_dev,
> struct tc_cls_flower_offload *tc)
> {
> struct efx_tc_action_set *act;
>
> /* parse the match */
>
> tcf_exts_for_each_action(i, a, tc->exts) {
> if (a->ops && a->ops->stats_update) {
> /* act is the hw action we're building */
> act->count = allocate_a_counter();
Also, this was actually taking a->tcfa_index, allowing multiple rules to
share a counter. The action index doesn't seem to be available in the
new flow_offload API.
-Ed
next prev parent reply other threads:[~2019-04-25 13:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 19:41 TC stats / hw offload question Edward Cree
2019-02-06 2:20 ` Jamal Hadi Salim
2019-02-08 10:26 ` Edward Cree
2019-02-09 17:39 ` Jamal Hadi Salim
2019-02-11 11:44 ` Edward Cree
2019-02-14 12:39 ` Jamal Hadi Salim
2019-02-14 15:17 ` Andy Gospodarek
2019-02-18 18:56 ` Edward Cree
2019-02-18 19:37 ` Edward Cree
2019-04-24 14:05 ` Edward Cree
2019-04-24 14:11 ` Pablo Neira Ayuso
2019-04-24 15:03 ` Edward Cree
2019-04-25 13:23 ` Edward Cree [this message]
2019-04-25 22:33 ` Pablo Neira Ayuso
2019-04-26 12:13 ` Edward Cree
2019-04-26 12:42 ` Jamal Hadi Salim
2019-04-26 18:49 ` Pablo Neira Ayuso
2019-04-29 14:11 ` Edward Cree
2019-04-29 15:21 ` Pablo Neira Ayuso
2019-04-29 16:25 ` Edward Cree
2019-04-29 19:14 ` Pablo Neira Ayuso
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=58c74d0f-b92e-31f9-9828-24fb04129534@solarflare.com \
--to=ecree@solarflare.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=xiyou.wangcong@gmail.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).