From: Jiri Pirko <jiri@resnulli.us>
To: Edward Cree <ecree@solarflare.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
Anjali Singhai Jain <anjali.singhai@intel.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Or Gerlitz <gerlitz.or@gmail.com>
Subject: Re: [RFC PATCH net-next 0/3] flow_offload: Re-add various features that disappeared
Date: Sat, 4 May 2019 07:48:07 +0200 [thread overview]
Message-ID: <20190504054807.GB2189@nanopsycho> (raw)
In-Reply-To: <alpine.LFD.2.21.1905031538070.11823@ehc-opti7040.uk.solarflarecom.com>
Fri, May 03, 2019 at 04:59:28PM CEST, ecree@solarflare.com wrote:
>When the flow_offload infrastructure was added, a couple of things that
> were previously possible for drivers to support in TC offload were not
> plumbed through, perhaps because the drivers in the tree did not fully
> or correctly implement them.
>The main issue was with statistics; in TC (and in the previous offload
> API) statistics are per-action, though generally only on 'delivery'
> actions like mirred, ok and shot. Actions also have an index, which
> may be supplied by the user, which allows the sharing of entities such
> as counters between multiple rules. The existing driver implementations
> did not support this, however, instead allocating a single counter per
> rule. The flow_offload API did not support this either, as (a) the
> action index never reached the driver, and (b) the TC_CLSFLOWER_STATS
> callback was only able to return a single set of stats which were added
> to all counters for actions on the rule. Patch #1 of this series fixes
> (a) by storing tcfa_index in a new action_index member of struct
> flow_action_entry, while patch #2 fixes (b) by adding a new callback,
> TC_CLSFLOWER_STATS_BYINDEX, which retrieves statistics for a specified
> action_index rather than by rule (although the rule cookie is still
> passed as well).
>Patch #3 adds flow_rule_match_cvlan(), analogous to
> flow_rule_match_vlan() but accessing FLOW_DISSECTOR_KEY_CVLAN instead
> of FLOW_DISSECTOR_KEY_VLAN, to allow offloading inner VLAN matches.
>This patch series does not include any users of these new interfaces;
> the driver in which I hope to use them does not yet exist upstream as
> it is for hardware which is still under development. However I've CCed
> developers of various other drivers that implement TC offload, in case
> any of them want to implement support. Otherwise I imagine that David
> won't be willing to take this without a user, in which case I'll save
> it to submit alongside the aforementioned unfinished driver (hence the
> RFC tags for now).
We need in-tree users of the API.
>
>Edward Cree (3):
> flow_offload: copy tcfa_index into flow_action_entry
> flow_offload: restore ability to collect separate stats per action
> flow_offload: support CVLAN match
>
> include/net/flow_offload.h | 3 +++
> include/net/pkt_cls.h | 2 ++
> net/core/flow_offload.c | 7 +++++++
> net/sched/cls_api.c | 1 +
> net/sched/cls_flower.c | 30 ++++++++++++++++++++++++++++++
> 5 files changed, 43 insertions(+)
next prev parent reply other threads:[~2019-05-04 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 14:59 [RFC PATCH net-next 0/3] flow_offload: Re-add various features that disappeared Edward Cree
2019-05-04 5:48 ` Jiri Pirko [this message]
2019-05-04 6:23 ` Jakub Kicinski
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=20190504054807.GB2189@nanopsycho \
--to=jiri@resnulli.us \
--cc=andy@greyhouse.net \
--cc=anjali.singhai@intel.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=gerlitz.or@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--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).