From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org, ogerlitz@mellanox.com,
hadarh@mellanox.com, jiri@mellanox.com,
gospo@cumulusnetworks.com, jesse.brandeburg@intel.com,
john.r.fastabend@intel.com, amirv@mellanox.com
Subject: Re: [PATCH net-next 0/9] Mellanox 100G SRIOV offloads vlan push/pop
Date: Fri, 23 Sep 2016 07:22:42 -0400 (EDT) [thread overview]
Message-ID: <20160923.072242.1517007394054835660.davem@davemloft.net> (raw)
In-Reply-To: <1474563709-17943-1-git-send-email-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Thu, 22 Sep 2016 20:01:40 +0300
> From Or Gerlitz:
>
> This series further enhances the SRIOV TC offloads of mlx5 to handle
> the TC vlan push and pop actions. This serves a common use-case in
> virtualization systems where the virtual switch add (push) vlan tags
> to packets sent from VMs and removes (pop) vlan tags before the packet
> is received by the VM. We use the new E-Switch switchdev mode and the
> TC vlan action to achieve that also in SW defined SRIOV environments by
> offloading TC rules that contain this action along with forwarding
> (TC mirred/redirect action) the packet.
>
> In the first patch we add some helpers to access the TC vlan action info
> by offloading drivers. The next five patches don't add any new functionality,
> they do some refactoring and cleanups in the current code to be used next.
>
> The seventh patch deals with supporting vlans by the mlx5 e-switch in switchdev
> mode. The eighth patch does the vlan action offload from TC and the last patch
> adds matching for vlans as typically required by TC flows that involve vlan
> pop action.
>
> The series was applied on top of commit 524605e "cxgb4: Convert to use simple_open()"
Series applied, thanks.
prev parent reply other threads:[~2016-09-23 11:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 17:01 [PATCH net-next 0/9] Mellanox 100G SRIOV offloads vlan push/pop Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 1/9] net_sched: act_vlan: add helper inlines to access tcf_vlan info Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 2/9] net/mlx5: E-Switch, Set the vport when registering the uplink rep Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 3/9] net/mlx5: E-Switch, Set vport representor fields explicitly on registration Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 4/9] net/mlx5: E-Switch, Allow fine tuning of eswitch vport push/pop vlan Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 5/9] net/mlx5: Put elements related to offloaded TC rule in one struct Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 6/9] net/mlx5e: Refactor retrival of skb from rx completion element (cqe) Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 7/9] net/mlx5: E-Switch, Support VLAN actions in the offloads mode Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 8/9] net/mlx5e: Add TC vlan action for SRIOV offloads Saeed Mahameed
2016-09-22 17:01 ` [PATCH net-next 9/9] net/mlx5e: Add TC vlan match parsing Saeed Mahameed
2016-09-23 11:22 ` David Miller [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=20160923.072242.1517007394054835660.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=gospo@cumulusnetworks.com \
--cc=hadarh@mellanox.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@mellanox.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=saeedm@mellanox.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).