Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Mark Bloch <markb@mellanox.com>
To: Parav Pandit <parav@mellanox.com>,
	Leon Romanovsky <leonro@mellanox.com>,
	Saeed Mahameed <saeedm@mellanox.com>
Cc: Jason Gunthorpe <jgg@mellanox.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Maor Gottlieb <maorg@mellanox.com>
Subject: Re: [PATCH V2 mlx5-next 09/11] net/mlx5: Eswitch, enable RoCE loopback traffic
Date: Mon, 29 Apr 2019 22:30:36 +0000	[thread overview]
Message-ID: <e08a2f83-03ac-61cf-322f-652f4549e074@mellanox.com> (raw)
In-Reply-To: <VI1PR0501MB22712A3E3743FE283308771ED1390@VI1PR0501MB2271.eurprd05.prod.outlook.com>



On 4/29/19 11:45 AM, Parav Pandit wrote:
> 
> 
>> -----Original Message-----
>> From: netdev-owner@vger.kernel.org <netdev-owner@vger.kernel.org> On
>> Behalf Of Leon Romanovsky
>> Sent: Monday, April 29, 2019 1:41 PM
>> To: Saeed Mahameed <saeedm@mellanox.com>
>> Cc: Jason Gunthorpe <jgg@mellanox.com>; netdev@vger.kernel.org; linux-
>> rdma@vger.kernel.org; Maor Gottlieb <maorg@mellanox.com>; Mark Bloch
>> <markb@mellanox.com>
>> Subject: Re: [PATCH V2 mlx5-next 09/11] net/mlx5: Eswitch, enable RoCE
>> loopback traffic
>>
>> On Mon, Apr 29, 2019 at 06:14:16PM +0000, Saeed Mahameed wrote:
>>> From: Maor Gottlieb <maorg@mellanox.com>
>>>
>>> When in switchdev mode, we would like to treat loopback RoCE traffic
>>> (on eswitch manager) as RDMA and not as regular Ethernet traffic In
>>> order to enable it we add flow steering rule that forward RoCE
>>> loopback traffic to the HW RoCE filter (by adding allow rule).
>>> In addition we add RoCE address in GID index 0, which will be set in
>>> the RoCE loopback packet.
>>>
> I likely don't understand nor I reviewed the patches.
> Part that I don't understand is GID index 0 for RoCE.
> RoCE traffic runs over all the GID entries and for all practical purposes from non_zero index.
> How will it work?

Currently in switchdev mode we only support RAW Ethernet QP and no RoCE capabilities are reported to ib_core.
Which means no GIDs are inserted to the HW's GID table and RoCE isn't enabled on the vport.

However, there are cases where an internal RC QP might be needed, and for that we need a GID.
The patches from Maor make sure a GID entry at index 0 is valid (and we do that only in switchdev mode),
and with steering we make sure such traffic is only used for loopback purposes.

Mark
 
> It is better if you explain it in the commit log, why its done this way, 'what' part is already present the patch.
> 
> 
>>> Signed-off-by: Maor Gottlieb <maorg@mellanox.com>
>>> Reviewed-by: Mark Bloch <markb@mellanox.com>
>>> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
>>> ---
>>>  .../net/ethernet/mellanox/mlx5/core/Makefile  |   2 +-
>>>  .../mellanox/mlx5/core/eswitch_offloads.c     |   4 +
>>>  .../net/ethernet/mellanox/mlx5/core/rdma.c    | 182 ++++++++++++++++++
>>>  .../net/ethernet/mellanox/mlx5/core/rdma.h    |  20 ++
>>>  include/linux/mlx5/driver.h                   |   7 +
>>>  5 files changed, 214 insertions(+), 1 deletion(-)  create mode 100644
>>> drivers/net/ethernet/mellanox/mlx5/core/rdma.c
>>>  create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/rdma.h
>>>
>>
>> Thanks,
>> Acked-by: Leon Romanovsky <leonro@mellanox.com>

  reply	other threads:[~2019-04-29 22:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29 18:13 [PATCH V2 mlx5-next 00/11] Mellanox, mlx5-next updates 2019-04-25 Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 01/11] net/mlx5: E-Switch: Introduce prio tag mode Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 02/11] net/mlx5: Get rid of storing copy of device name Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 03/11] net/mlx5: Separate and generalize dma device from pci device Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 04/11] IB/mlx5: Restrict 'DELAY_DROP_TIMEOUT' subtype to Ethernet interfaces Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 05/11] net/mlx5: Enable general events on all interfaces Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 06/11] net/mlx5: Pass flow steering objects to fs_cmd Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 07/11] net/mlx5: Add support in RDMA RX steering Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 08/11] net/mlx5: Add new miss flow table action Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 09/11] net/mlx5: Eswitch, enable RoCE loopback traffic Saeed Mahameed
2019-04-29 18:41   ` Leon Romanovsky
2019-04-29 18:45     ` Parav Pandit
2019-04-29 22:30       ` Mark Bloch [this message]
2019-04-29 22:34         ` Parav Pandit
2019-04-29 18:14 ` [PATCH V2 mlx5-next 10/11] net/mlx5: Geneve, Add basic Geneve encap/decap flow table capabilities Saeed Mahameed
2019-04-29 18:14 ` [PATCH V2 mlx5-next 11/11] net/mlx5: Geneve, Add flow table capabilities for Geneve decap with TLV options Saeed Mahameed
2019-04-29 23:56 ` [PATCH V2 mlx5-next 00/11] Mellanox, mlx5-next updates 2019-04-25 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=e08a2f83-03ac-61cf-322f-652f4549e074@mellanox.com \
    --to=markb@mellanox.com \
    --cc=jgg@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maorg@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=parav@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