All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, saeedm@mellanox.com,
	leon@kernel.org, michael.chan@broadcom.com, vishal@chelsio.com,
	jeffrey.t.kirsher@intel.com, idosch@mellanox.com,
	aelior@marvell.com, peppe.cavallaro@st.com,
	alexandre.torgue@st.com, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, pablo@netfilter.org,
	ecree@solarflare.com, mlxsw@mellanox.com
Subject: [patch net-next v4 01/10] flow_offload: Introduce offload of HW stats type
Date: Sat,  7 Mar 2020 12:40:11 +0100	[thread overview]
Message-ID: <20200307114020.8664-2-jiri@resnulli.us> (raw)
In-Reply-To: <20200307114020.8664-1-jiri@resnulli.us>

From: Jiri Pirko <jiri@mellanox.com>

Initially, pass "ANY" (struct is zeroed) to the drivers as that is the
current implicit value coming down to flow_offload. Add a bool
indicating that entries have mixed HW stats type.

Signed-off-by: Jiri Pirko <jiri@mellanox.com>
---
v3->v4:
- fixed member alignment
v2->v3:
- moved to bitfield
- removed "mixed" bool
v1->v2:
- moved to actions
- add mixed bool
---
 include/net/flow_offload.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/include/net/flow_offload.h b/include/net/flow_offload.h
index cd3510ac66b0..93d17f37e980 100644
--- a/include/net/flow_offload.h
+++ b/include/net/flow_offload.h
@@ -154,6 +154,8 @@ enum flow_action_mangle_base {
 	FLOW_ACT_MANGLE_HDR_TYPE_UDP,
 };
 
+#define FLOW_ACTION_HW_STATS_TYPE_ANY 0
+
 typedef void (*action_destr)(void *priv);
 
 struct flow_action_cookie {
@@ -168,6 +170,7 @@ void flow_action_cookie_destroy(struct flow_action_cookie *cookie);
 
 struct flow_action_entry {
 	enum flow_action_id		id;
+	u8				hw_stats_type;
 	action_destr			destructor;
 	void				*destructor_priv;
 	union {
-- 
2.21.1


  reply	other threads:[~2020-03-07 11:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 11:40 [patch net-next v4 00/10] net: allow user specify TC action HW stats type Jiri Pirko
2020-03-07 11:40 ` Jiri Pirko [this message]
2020-03-09 16:52   ` [patch net-next v4 01/10] flow_offload: Introduce offload of " Edward Cree
2020-03-09 17:34     ` Jiri Pirko
2020-03-09 17:46       ` Edward Cree
2020-03-10 11:19         ` Jiri Pirko
2020-03-09 21:36     ` Jakub Kicinski
2020-03-09 22:27       ` Edward Cree
2020-03-09 22:38         ` Jakub Kicinski
2020-03-10 11:22           ` Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 02/10] ocelot_flower: use flow_offload_has_one_action() helper Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 03/10] flow_offload: check for basic action hw stats type Jiri Pirko
2020-03-09 10:23   ` Jose Abreu
2020-03-09 12:04     ` Jiri Pirko
2020-03-09 13:31       ` Jose Abreu
2020-03-09 13:43         ` Jiri Pirko
2020-03-09 16:52   ` Edward Cree
2020-03-09 17:32     ` Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 04/10] mlxsw: spectrum_flower: Do not allow mixing HW stats types for actions Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 05/10] mlxsw: restrict supported HW stats type to "any" Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 06/10] flow_offload: introduce "immediate" HW stats type and allow it in mlxsw Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 07/10] flow_offload: introduce "delayed" HW stats type and allow it in mlx5 Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 08/10] mlxsw: spectrum_acl: Ask device for rule stats only if counter was created Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 09/10] flow_offload: introduce "disabled" HW stats type and allow it in mlxsw Jiri Pirko
2020-03-07 11:40 ` [patch net-next v4 10/10] sched: act: allow user to specify type of HW stats for a filter Jiri Pirko
2020-03-09  4:09 ` [patch net-next v4 00/10] net: allow user specify TC action HW stats type David Miller

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=20200307114020.8664-2-jiri@resnulli.us \
    --to=jiri@resnulli.us \
    --cc=aelior@marvell.com \
    --cc=alexandre.torgue@st.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=idosch@mellanox.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jhs@mojatatu.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=peppe.cavallaro@st.com \
    --cc=saeedm@mellanox.com \
    --cc=vishal@chelsio.com \
    --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 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.