From: "Rupert Dance" <rsdance-rzwDkyJvnYokmLvzuZlaBw@public.gmane.org>
To: 'Ram Amrani' <Ram.Amrani-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: How to RoCE v2?
Date: Mon, 13 Jul 2015 08:26:12 -0400 [thread overview]
Message-ID: <001201d0bd67$1b8a6440$529f2cc0$@soft-forge.com> (raw)
In-Reply-To: <3CBF78CA47A0D542A0094940BB0205E762D284-yWqByQLCgs06wu3ARrlbmA@public.gmane.org>
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-2015070
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/OFED-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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
[mailto:linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of Ram Amrani
Sent: Monday, July 13, 2015 7:47 AM
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-13 12:26 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 [this message]
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
[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='001201d0bd67$1b8a6440$529f2cc0$@soft-forge.com' \
--to=rsdance-rzwdkyjvnyokmlvzuzlabw@public.gmane.org \
--cc=Ram.Amrani-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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.