All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Ram Amrani <Ram.Amrani-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
To: Devesh Sharma
	<devesh.sharma-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org>,
	Rupert Dance <rsdance-rzwDkyJvnYokmLvzuZlaBw@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: How to RoCE v2?
Date: Tue, 14 Jul 2015 12:15:47 +0000	[thread overview]
Message-ID: <3CBF78CA47A0D542A0094940BB0205E762D78A@AVMB1.qlogic.org> (raw)
In-Reply-To: <CANjDDBiF6yj+mZwbCX61gmjf=nE6PD96ujN8t8sV_qg_LA6Qwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3808 bytes --]

Thanks Robert, Rupert and Devesh.

Where can I access the patches under review?



-----Original Message-----
From: Devesh Sharma [mailto:devesh.sharma@avagotech.com]
Sent: Monday, July 13, 2015 3:36 PM
To: Rupert Dance
Cc: Ram Amrani; linux-rdma@vger.kernel.org
Subject: Re: How to RoCE v2?

Hi Ram,

RoCE-v2 patch series is still under review, you should see updated patch series soon on this mailing list.

-Regards
Devesh

On Mon, Jul 13, 2015 at 5:56 PM, Rupert Dance <rsdance@soft-forge.com> wrote:
> Hi Ram,
>
> There were several issues discovered in OFED 3.18 RC3 which have been
> resolved in the latest daily build.
>
> https://www.openfabrics.org/downloads/OFED/ofed-3.18-daily/OFED-3.18-2
> 015070
> 7-2235.tgz
>
> The issues are documented in the latest bugs in Bugzilla:
>
> http://bugs.openfabrics.org/bugzilla/
>
> There are also additional notes about the build procedures in the
> following
> document:
>
> https://www.openfabrics.org/downloads/WorkGroups/ewg/Build%20Process/O
> FED-3-
> 18-Build%20process-v3.pdf
>
> Finally we hope to have full support for RoCE v2 in out next major
> OFED Build which will be based on the 4.x kernel.
>
> Thanks
>
> Rupert
>
> -----Original Message-----
> From: linux-rdma-owner@vger.kernel.org
> [mailto:linux-rdma-owner@vger.kernel.org] On Behalf Of Ram Amrani
> Sent: Monday, July 13, 2015 7:47 AM
> To: linux-rdma@vger.kernel.org
> Subject: How to RoCE v2?
>
> Hi,
> This is my first e-mail on this list. I have a few questions that I
> hope you'll answer -
>
> In the latest OFED (3.18-rc3) I don't see any RoCE v2 code, albeit it
> being introduce in 2014. How come?
>
> I've been unable to track patches from e-mail archives about relevant
> e-mails such as "[PATCH 0/2] Adding support for RoCE V2 specification".
> Where can patches be found/tracked? Is there a git repository with log?
>
> I've also tried to build the latest OFED, in the hope that it will
> contain the RoCE 2 code, but got errors. I followed the instructions
> in the web
> (https://www.openfabrics.org/index.php/installation.html) but got
> errors when applying patches ("./scripts/admin_rdma.sh -n -p") and
> also when skipping it and running configure and make... are the
> instructions up-to-date?
>
> Thanks,
>
> Ram
>
>
> ________________________________
>
> This message and any attached documents contain information from the
> sending company or its parent company(s), subsidiaries, divisions or
> branch offices that may be confidential. If you are not the intended
> recipient, you may not read, copy, distribute, or use this
> information. If you have received this transmission in error, please
> notify the sender immediately by reply e-mail and then delete this message.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma"
> in the body of a message to majordomo@vger.kernel.org More majordomo
> info at http://vger.kernel.org/majordomo-info.html
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma"
> in the body of a message to majordomo@vger.kernel.org More majordomo
> info at  http://vger.kernel.org/majordomo-info.html

________________________________

This message and any attached documents contain information from the sending company or its parent company(s), subsidiaries, divisions or branch offices that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.
N‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·¥Š{±­ÙšŠ{ayº\x1dʇڙë,j\a­¢f£¢·hš‹»öì\x17/oSc¾™Ú³9˜uÀ¦æå‰È&jw¨®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿïêäz¹Þ–Šàþf£¢·hšˆ§~ˆmš

  parent reply	other threads:[~2015-07-14 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 11:47 How to RoCE v2? Ram Amrani
     [not found] ` <3CBF78CA47A0D542A0094940BB0205E762D284-yWqByQLCgs06wu3ARrlbmA@public.gmane.org>
2015-07-13 12:26   ` Rupert Dance
2015-07-13 12:36     ` Devesh Sharma
     [not found]       ` <CANjDDBiF6yj+mZwbCX61gmjf=nE6PD96ujN8t8sV_qg_LA6Qwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-14 12:15         ` Ram Amrani [this message]
     [not found]           ` <3CBF78CA47A0D542A0094940BB0205E762D78A-yWqByQLCgs06wu3ARrlbmA@public.gmane.org>
2015-07-14 17:54             ` Devesh Sharma
2015-07-13 16:50   ` Woodruff, Robert J

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=3CBF78CA47A0D542A0094940BB0205E762D78A@AVMB1.qlogic.org \
    --to=ram.amrani-h88zbnxc6kdqt0dzr+alfa@public.gmane.org \
    --cc=devesh.sharma-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rsdance-rzwDkyJvnYokmLvzuZlaBw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.