linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Achiad Shochat <achiad-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Tom Talpey <tom-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org>,
	Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
	Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Haggai Eran <haggaie-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Somnath Kotur
	<Somnath.Kotur-idTK6quXuVS1Z/+hSey0Gg@public.gmane.org>
Subject: Re: [PATCH for-next 00/10] Add RoCE support to the mlx5 driver
Date: Tue, 25 Aug 2015 11:35:14 +0300	[thread overview]
Message-ID: <55DC28C2.4020705@mellanox.com> (raw)
In-Reply-To: <55DB8152.6080402-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org>

On 8/24/2015 11:40 PM, Tom Talpey wrote:
> On 8/20/2015 12:46 PM, Achiad Shochat wrote:
>> Hi Doug,
>>
>> This patchset adds RoCE V1 and RoCE V2 support to the mlx5 device
>> driver.
>
> Question - assuming I read them correctly, these patches add the
> RoCE v1 and RoCE v2 support on a per-port basis. That is, a port
> can be either IB, RoCE v1 or RoCE v2, but not a combination.
>
> Has any thought been put toward supporting these protocols on a
> per-QP basis, i.e. the caller of rdma_connect() can specify the
> desired protocol? Or to have some sort of discovery?
>
> I know that there may be implementation restrictions on today's
> devices, but it's my personal belief that future devices will
> support multiple protocols (perhaps beyond the three above), and
> laying the groundwork for this today will be important.
>
> Tom.
>
>>
>> This patchset was applied and tested over patchset "Add RoCE v2
>> support" which was sent to the mailing list by Matan Barak.
>>
>> Achiad Shochat (10):
>>    IB/mlx5: Support IB device's callback for getting the link layer
>>    IB/mlx5: Support IB device's callback for getting its netdev
>>    net/mlx5_core: Break down the vport mac address query function
>>    net/mlx5_core: Introduce access functions to enable/disable RoCE
>>    net/mlx5_core: Introduce access functions to query vport RoCE fields
>>    IB/mlx5: Extend query_device/port to support RoCE
>>    IB/mlx5: Set network_hdr_type upon RoCE responder completion
>>    IB/mlx5: Support IB device's callbacks for adding/deleting GIDs
>>    IB/mlx5: Add RoCE fields to Address Vector
>>    IB/mlx5: Support RoCE
>>
>>   drivers/infiniband/hw/mlx5/ah.c                 |  32 ++-
>>   drivers/infiniband/hw/mlx5/cq.c                 |  17 ++
>>   drivers/infiniband/hw/mlx5/main.c               | 318
>> ++++++++++++++++++++++--
>>   drivers/infiniband/hw/mlx5/mlx5_ib.h            |  15 +-
>>   drivers/infiniband/hw/mlx5/qp.c                 |  42 +++-
>>   drivers/net/ethernet/mellanox/mlx5/core/vport.c | 139 ++++++++++-
>>   include/linux/mlx5/device.h                     |  26 ++
>>   include/linux/mlx5/driver.h                     |   7 -
>>   include/linux/mlx5/mlx5_ifc.h                   |  10 +-
>>   include/linux/mlx5/qp.h                         |  21 +-
>>   include/linux/mlx5/vport.h                      |   8 +
>>   11 files changed, 578 insertions(+), 57 deletions(-)
>>
>

Hello Tom,

RoCE v1 and RoCE v2 are supported on a per-GID basis, not sure what got 
you to understand it is per-port.

Achiad

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-08-25  8:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 16:46 [PATCH for-next 00/10] Add RoCE support to the mlx5 driver Achiad Shochat
     [not found] ` <1440089189-3361-1-git-send-email-achiad-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-08-20 16:46   ` [PATCH for-next 01/10] IB/mlx5: Support IB device's callback for getting the link layer Achiad Shochat
2015-08-20 16:46   ` [PATCH for-next 02/10] IB/mlx5: Support IB device's callback for getting its netdev Achiad Shochat
     [not found]     ` <1440089189-3361-3-git-send-email-achiad-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-10-11 13:32       ` Matan Barak
2015-08-20 16:46   ` [PATCH for-next 03/10] net/mlx5_core: Break down the vport mac address query function Achiad Shochat
2015-08-20 16:46   ` [PATCH for-next 04/10] net/mlx5_core: Introduce access functions to enable/disable RoCE Achiad Shochat
2015-08-20 16:46   ` [PATCH for-next 05/10] net/mlx5_core: Introduce access functions to query vport RoCE fields Achiad Shochat
2015-08-20 16:46   ` [PATCH for-next 06/10] IB/mlx5: Extend query_device/port to support RoCE Achiad Shochat
2015-08-20 16:46   ` [PATCH for-next 07/10] IB/mlx5: Set network_hdr_type upon RoCE responder completion Achiad Shochat
2015-08-20 16:46   ` [PATCH for-next 08/10] IB/mlx5: Support IB device's callbacks for adding/deleting GIDs Achiad Shochat
2015-08-20 16:46   ` [PATCH for-next 09/10] IB/mlx5: Add RoCE fields to Address Vector Achiad Shochat
2015-08-20 16:46   ` [PATCH for-next 10/10] IB/mlx5: Support RoCE Achiad Shochat
2015-08-24 20:40   ` [PATCH for-next 00/10] Add RoCE support to the mlx5 driver Tom Talpey
     [not found]     ` <55DB8152.6080402-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org>
2015-08-25  8:35       ` Achiad Shochat [this message]
     [not found]         ` <55DC28C2.4020705-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-08-25 12:32           ` Tom Talpey
     [not found]             ` <55DC6040.5080907-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org>
2015-08-25 13:06               ` Achiad Shochat
     [not found]                 ` <55DC685A.8060402-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-08-26  5:31                   ` Haggai Eran

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=55DC28C2.4020705@mellanox.com \
    --to=achiad-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=Somnath.Kotur-idTK6quXuVS1Z/+hSey0Gg@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=haggaie-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=tom-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.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).