From: "Woodruff, Robert J" <robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Ram Amrani <Ram.Amrani-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: How to RoCE v2?
Date: Mon, 13 Jul 2015 16:50:59 +0000 [thread overview]
Message-ID: <9C6B67F36DCAFC479B1CF6A967258A8C7D207932@ORSMSX110.amr.corp.intel.com> (raw)
In-Reply-To: <3CBF78CA47A0D542A0094940BB0205E762D284-yWqByQLCgs06wu3ARrlbmA@public.gmane.org>
Ram Amrani wrote,
>In the latest OFED (3.18-rc3) I don't see any RoCE v2 code, albeit it being introduce in 2014. How come?
These patches have not yet been accepted upstream and since OFED now pulls the kernel code from upstream,
It is not yet in OFED-3.18 that was based on the kernel.org 3.18 kernel.
I am hoping that the RoCE v2 patches will be ready for the next major OFED, that will likely be based on the kernel.org
4.2 or 4.3 kernel.
--
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
prev parent reply other threads:[~2015-07-13 16:50 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
[not found] ` <3CBF78CA47A0D542A0094940BB0205E762D78A-yWqByQLCgs06wu3ARrlbmA@public.gmane.org>
2015-07-14 17:54 ` Devesh Sharma
2015-07-13 16:50 ` Woodruff, Robert J [this message]
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=9C6B67F36DCAFC479B1CF6A967258A8C7D207932@ORSMSX110.amr.corp.intel.com \
--to=robert.j.woodruff-ral2jqcrhueavxtiumwx3w@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.