netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: Saeed Mahameed <saeedm@mellanox.com>,
	Leon Romanovsky <leonro@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: [PATCH mlx5-next 00/18] Mellanox, mlx5-next updates 28-10-2019
Date: Mon, 28 Oct 2019 23:34:54 +0000	[thread overview]
Message-ID: <20191028233440.5564-1-saeedm@mellanox.com> (raw)

Hi, 

This series refactors and tide up eswitch vport and ACL code to provide
better separation between eswitch legacy mode and switchdev mode 
implementation in mlx5, for better future scalability and introduction of
new switchdev mode functionality which might rely on shared structures
with legacy mode, such as vport ACL tables.

Summary:

1. Do vport ACL configuration on per vport basis when enabling/disabling a vport.
This enables to have vports enabled/disabled outside of eswitch config for future.

2. Split the code for legacy vs offloads mode and make it clear

3. Tide up vport locking and workqueue usage

4. Fix metadata enablement for ECPF

5. Make explicit use of VF property to publish IB_DEVICE_VIRTUAL_FUNCTION

In case of no objection this series will be applied to mlx5-next branch
and sent later as pull request to both rdma-next and net-next branches.

Thanks,
Saeed.

---

Parav Pandit (14):
  net/mlx5: E-switch, Introduce and use vlan rule config helper
  net/mlx5: Introduce and use mlx5_esw_is_manager_vport()
  net/mlx5: Correct comment for legacy fields
  net/mlx5: Move metdata fields under offloads structure
  net/mlx5: Move legacy drop counter and rule under legacy structure
  net/mlx5: Tide up state_lock and vport enabled flag usage
  net/mlx5: E-switch, Prepare code to handle vport enable error
  net/mlx5: E-switch, Legacy introduce and use per vport acl tables APIs
  net/mlx5: Move ACL drop counters life cycle close to ACL lifecycle
  net/mlx5: E-switch, Offloads introduce and use per vport acl tables
    APIs
  net/mlx5: Restrict metadata disablement to offloads mode
  net/mlx5: Refactor ingress acl configuration
  net/mlx5: E-switch, Enable metadata on own vport
  IB/mlx5: Introduce and use mlx5_core_is_vf()

Qing Huang (1):
  net/mlx5: Fixed a typo in a comment in esw_del_uc_addr()

Vu Pham (3):
  net/mlx5: E-Switch, Rename egress config to generic name
  net/mlx5: E-Switch, Rename ingress acl config in offloads mode
  net/mlx5: E-switch, Offloads shift ACL programming during
    enable/disable vport

 drivers/infiniband/hw/mlx5/main.c             |   2 +-
 .../net/ethernet/mellanox/mlx5/core/eswitch.c | 573 +++++++++++-------
 .../net/ethernet/mellanox/mlx5/core/eswitch.h |  66 +-
 .../mellanox/mlx5/core/eswitch_offloads.c     | 259 ++++----
 include/linux/mlx5/driver.h                   |   5 +
 5 files changed, 537 insertions(+), 368 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-10-28 23:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 23:34 Saeed Mahameed [this message]
2019-10-28 23:34 ` [PATCH mlx5-next 01/18] net/mlx5: Fixed a typo in a comment in esw_del_uc_addr() Saeed Mahameed
2019-10-28 23:34 ` [PATCH mlx5-next 02/18] net/mlx5: E-Switch, Rename egress config to generic name Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 03/18] net/mlx5: E-Switch, Rename ingress acl config in offloads mode Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 04/18] net/mlx5: E-switch, Introduce and use vlan rule config helper Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 05/18] net/mlx5: Introduce and use mlx5_esw_is_manager_vport() Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 06/18] net/mlx5: Correct comment for legacy fields Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 07/18] net/mlx5: Move metdata fields under offloads structure Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 08/18] net/mlx5: Move legacy drop counter and rule under legacy structure Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 09/18] net/mlx5: Tide up state_lock and vport enabled flag usage Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 10/18] net/mlx5: E-switch, Prepare code to handle vport enable error Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 11/18] net/mlx5: E-switch, Legacy introduce and use per vport acl tables APIs Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 12/18] net/mlx5: Move ACL drop counters life cycle close to ACL lifecycle Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 13/18] net/mlx5: E-switch, Offloads introduce and use per vport acl tables APIs Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 14/18] net/mlx5: E-switch, Offloads shift ACL programming during enable/disable vport Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 15/18] net/mlx5: Restrict metadata disablement to offloads mode Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 16/18] net/mlx5: Refactor ingress acl configuration Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 17/18] net/mlx5: E-switch, Enable metadata on own vport Saeed Mahameed
2019-10-28 23:35 ` [PATCH mlx5-next 18/18] IB/mlx5: Introduce and use mlx5_core_is_vf() Saeed Mahameed
2019-11-01 21:41 ` [PATCH mlx5-next 00/18] Mellanox, mlx5-next updates 28-10-2019 Saeed Mahameed

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=20191028233440.5564-1-saeedm@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).