From: John Fastabend <john.fastabend@gmail.com>
To: Amir Vadai <amir@vadai.me>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org,
John Fastabend <john.r.fastabend@intel.com>
Cc: Or Gerlitz <ogerlitz@mellanox.com>,
Hadar Har-Zion <hadarh@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Scott Feldman <sfeldma@gmail.com>
Subject: Re: [RFC net-next 2/9] net/switchdev: Introduce hardware offload support
Date: Mon, 01 Feb 2016 01:26:06 -0800 [thread overview]
Message-ID: <56AF24AE.8030101@gmail.com> (raw)
In-Reply-To: <1454315685-32202-3-git-send-email-amir@vadai.me>
On 16-02-01 12:34 AM, Amir Vadai wrote:
> Extend the switchdev API with new operations: switchdev_port_flow_add()
> and switchdev_port_flow_del().
> It allows the user to add/del a hardware offloaded flow classification
> and actions.
> For every new flow object a cookie is supplied. This cookie will be
> used later on to identify the flow when removed.
>
> In order to make the API as flexible as possible, flow_dissector is
> being used to describe the flow classifier.
>
> Every new flow object is consists of a flow_dissector+key+mask to
> describe the classifier and a switchdev_obj_port_flow_act to describe
> the actions and their attributes.
>
> object is passed to the lower layer driver to be pushed into the
> hardware.
>
> Signed-off-by: Amir Vadai <amir@vadai.me>
> ---
+Scott
[...]
> +struct switchdev_obj_port_flow {
> + struct switchdev_obj obj;
> +
> + unsigned long cookie;
> + struct flow_dissector *dissector; /* Dissector for mask and keys */
> + void *mask; /* Flow keys mask */
> + void *key; /* Flow keys */
The heavy use of void* here and below seems questionable to me. If your
going to consume flow keys/mask define them.
> + struct switchdev_obj_port_flow_act *actions;
> +};
[...]
next prev parent reply other threads:[~2016-02-01 9:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 8:34 [RFC net-next 0/9] TC filter HW offloads Amir Vadai
2016-02-01 8:34 ` [RFC net-next 1/9] net/flow_dissector: Make dissector_uses_key() and skb_flow_dissector_target() public Amir Vadai
2016-02-01 8:34 ` [RFC net-next 2/9] net/switchdev: Introduce hardware offload support Amir Vadai
2016-02-01 9:06 ` Jiri Pirko
2016-02-01 9:11 ` amirva
2016-02-01 9:26 ` John Fastabend [this message]
2016-02-01 8:34 ` [RFC net-next 3/9] net/act: Offload support by tc actions Amir Vadai
2016-02-01 8:34 ` [RFC net-next 4/9] net/act_skbedit: Introduce hardware offload support Amir Vadai
2016-02-01 8:34 ` [RFC net-next 5/9] net/act_gact: Introduce hardware offload support for drop Amir Vadai
2016-02-01 8:34 ` [RFC net-next 6/9] net/cls_flower: Introduce hardware offloading Amir Vadai
2016-02-01 9:31 ` John Fastabend
2016-02-01 9:47 ` John Fastabend
2016-02-01 10:43 ` Amir Vadai
2016-02-01 21:25 ` John Fastabend
2016-02-01 8:34 ` [RFC net-next 7/9] net/mlx5_core: Go to next flow table support Amir Vadai
2016-02-01 8:34 ` [RFC net-next 8/9] net/mlx5e: Introduce MLX5_FLOW_NAMESPACE_OFFLOADS Amir Vadai
2016-02-01 8:34 ` [RFC net-next 9/9] net/mlx5e: Flow steering support through switchdev Amir Vadai
2016-02-01 18:52 ` Saeed Mahameed
2016-02-01 21:45 ` Or Gerlitz
2016-02-01 9:21 ` [RFC net-next 0/9] TC filter HW offloads John Fastabend
2016-02-01 14:37 ` Amir Vadai
2016-02-01 19:59 ` Tom Herbert
2016-02-01 20:14 ` John Fastabend
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=56AF24AE.8030101@gmail.com \
--to=john.fastabend@gmail.com \
--cc=amir@vadai.me \
--cc=davem@davemloft.net \
--cc=hadarh@mellanox.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=sfeldma@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).