From: Jason Gunthorpe <jgg@mellanox.com>
To: Saeed Mahameed <saeedm@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Mark Bloch <markb@mellanox.com>
Subject: Re: [PATCH mlx5-next 2/6] IB/mlx5: Unify e-switch representors load approach between uplink and VFs
Date: Thu, 13 Dec 2018 03:37:06 +0000 [thread overview]
Message-ID: <20181213033701.GB2883@mellanox.com> (raw)
In-Reply-To: <20181213031141.12783-3-saeedm@mellanox.com>
On Wed, Dec 12, 2018 at 07:11:37PM -0800, Saeed Mahameed wrote:
> From: Mark Bloch <markb@mellanox.com>
>
> When in switchdev mode and the add function is called by the core
> level driver, make sure we only register the callbacks, but don't
> create the mlx5 IB device or initialize anything. With this change
> all the IB devices in switchdev mode are created only once the load
> callback is invoked by the e-switch core sub-module. This follows
> the design paradigm under which the all the Eth representors must
> be loaded before any of IB reprs is loaded.
>
> Signed-off-by: Mark Bloch <markb@mellanox.com>
> Acked-by: Or Gerlitz <ogerlitz@mellanox.com>
> Reviewed-by: Leon Romanovsky <leonro@mellanox.com>
> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
> ---
> drivers/infiniband/hw/mlx5/ib_rep.c | 11 ++++++++++-
> drivers/infiniband/hw/mlx5/main.c | 29 +++++++++-------------------
> drivers/infiniband/hw/mlx5/mlx5_ib.h | 1 -
> 3 files changed, 19 insertions(+), 22 deletions(-)
Why is this going in the shared branch? This looks like an IB patch??
Jason
next prev parent reply other threads:[~2018-12-13 3:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 3:11 [PATCH mlx5-next 0/6] mlx5 updates for shared branch 2018-12-12 Saeed Mahameed
2018-12-13 3:11 ` [PATCH mlx5-next 1/6] net/mlx5: Use lowercase 'X' for hex values Saeed Mahameed
2018-12-13 3:11 ` [PATCH mlx5-next 2/6] IB/mlx5: Unify e-switch representors load approach between uplink and VFs Saeed Mahameed
2018-12-13 3:37 ` Jason Gunthorpe [this message]
2018-12-13 3:41 ` Saeed Mahameed
2018-12-13 3:11 ` [PATCH mlx5-next 3/6] net/mlx5: E-Switch, Introduce flow counter affinity Saeed Mahameed
2018-12-13 3:11 ` [PATCH mlx5-next 4/6] net/mlx5: Split the activate lag function into two routines Saeed Mahameed
2018-12-13 3:11 ` [PATCH mlx5-next 5/6] net/mlx5: Add lag affinity info to log Saeed Mahameed
2018-12-13 3:11 ` [PATCH mlx5-next 6/6] net/mlx5: Fold the modify lag code into function Saeed Mahameed
2018-12-14 19:05 ` [PATCH mlx5-next 0/6] mlx5 updates for shared branch 2018-12-12 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=20181213033701.GB2883@mellanox.com \
--to=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=markb@mellanox.com \
--cc=netdev@vger.kernel.org \
--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