From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Don Hiatt <don.hiatt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH rdma-next v3 0/3] Enhance IB CM to support OPA extended LIDs
Date: Fri, 11 Aug 2017 11:56:38 -0400 [thread overview]
Message-ID: <1502466998.3080.44.camel@redhat.com> (raw)
In-Reply-To: <1496943484-44065-1-git-send-email-don.hiatt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On Thu, 2017-06-08 at 13:38 -0400, Don Hiatt wrote:
> This patch series adds enhancements to support extended LIDs in the
> IB CM protocol. The core idea is to trasmit extended LIDs as OPA GIDs
> on the wire in the primary_local_gid, primary_remote_gid,
> alternate_local_gid and alternate_remote_gid fields of a CM request.
> On the receiving side, the extended LID is retrieved from these
> gids when processing the connection request.
Hi Don,
Thanks, series applied.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
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:[~2017-08-11 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 17:38 [PATCH rdma-next v3 0/3] Enhance IB CM to support OPA extended LIDs Don Hiatt
[not found] ` <1496943484-44065-1-git-send-email-don.hiatt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-06-08 17:38 ` [PATCH rdma-next v3 1/3] IB/CM: Add OPA Path record support to CM Don Hiatt
2017-06-08 17:38 ` [PATCH rdma-next v3 2/3] IB/CM: Create appropriate path records when handling CM request Don Hiatt
2017-06-08 17:38 ` [PATCH rdma-next v3 3/3] IB/CM: Set appropriate slid and dlid " Don Hiatt
2017-08-11 15:56 ` Doug Ledford [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=1502466998.3080.44.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=don.hiatt-ral2JQCrhuEAvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox