linux-rdma.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: Jiri Pirko <jiri@mellanox.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: [PATCH mlx5-next 0/5] Mellanox, mlx5 roce enable devlink parameter
Date: Fri, 8 Nov 2019 23:45:17 +0000	[thread overview]
Message-ID: <20191108234451.31660-1-saeedm@mellanox.com> (raw)

Hi All,

Currently RoCE is always enabled by default in mlx5 and there is no option
for the user to disable it.

This change introduces new generic devlink param "enable_roce". 
User should set desired param value and reload the driver to get
desired configuration.

Two options for reload:
1) reload mlx5_ib driver.
2) reload via devlink, once the devlink mlx5 reload support [1]
lands in net-next branch, after this series is applied.

mlx5 devlink reload is not part of this patchset since it depends on
changes from net-next tree.

RoCE will still be enabled by default after this change.

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.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git/commit/?h=net-next-mlx5&id=0915d89b86e379b26457ba50656e9257193eaa60

Thanks,
Saeed.

---

Michael Guralnik (5):
  devlink: Add new "enable_roce" generic device param
  net/mlx5: Document flow_steering_mode devlink param
  net/mlx5: Handle "enable_roce" devlink param
  IB/mlx5: Rename profile and init methods
  IB/mlx5: Load profile according to RoCE enablement state

 .../device_drivers/mellanox/mlx5.rst          | 21 ++++++++++
 .../networking/devlink-params-mlx5.txt        | 17 ++++++++
 Documentation/networking/devlink-params.txt   |  4 ++
 drivers/infiniband/hw/mlx5/ib_rep.c           |  2 +-
 drivers/infiniband/hw/mlx5/ib_rep.h           |  2 +-
 drivers/infiniband/hw/mlx5/main.c             | 39 ++++++++++---------
 .../net/ethernet/mellanox/mlx5/core/devlink.c | 22 +++++++++++
 include/linux/mlx5/driver.h                   | 11 ++++++
 include/net/devlink.h                         |  4 ++
 net/core/devlink.c                            |  5 +++
 10 files changed, 106 insertions(+), 21 deletions(-)
 create mode 100644 Documentation/networking/devlink-params-mlx5.txt

-- 
2.21.0


             reply	other threads:[~2019-11-08 23:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 23:45 Saeed Mahameed [this message]
2019-11-08 23:45 ` [PATCH mlx5-next 1/5] devlink: Add new "enable_roce" generic device param Saeed Mahameed
2019-11-08 23:45 ` [PATCH mlx5-next 2/5] net/mlx5: Document flow_steering_mode devlink param Saeed Mahameed
2019-11-08 23:45 ` [PATCH mlx5-next 3/5] net/mlx5: Handle "enable_roce" " Saeed Mahameed
2019-11-08 23:45 ` [PATCH mlx5-next 4/5] IB/mlx5: Rename profile and init methods Saeed Mahameed
2019-11-08 23:45 ` [PATCH mlx5-next 5/5] IB/mlx5: Load profile according to RoCE enablement state Saeed Mahameed
2019-11-11 20:18 ` [PATCH mlx5-next 0/5] Mellanox, mlx5 roce enable devlink parameter 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=20191108234451.31660-1-saeedm@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=jiri@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).