From: Don Hiatt <don.hiatt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH rdma-next v3 0/3] Enhance IB CM to support OPA extended LIDs
Date: Thu, 8 Jun 2017 13:38:01 -0400 [thread overview]
Message-ID: <1496943484-44065-1-git-send-email-don.hiatt@intel.com> (raw)
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.
Changes from v2:
---------------
* Replace repeated record type logic with cm_path_set_rec_type().
Changes from v1:
---------------
* Replace 'IB/CM: Convert OPA Path record to IB during CM request'
with Patch 1 to add OPA path record support to CM.
* Remove 'IB/CM: Change sgid to IB GID when handling CM request'
as it is no longer need with the introduction of Patch 1.
The patches are organized as follows:
* Patch 1 adds OPA path record support to the Connection Manager.
* Patch 2 creates OPA path records when handling a connection request
if the request contained OPA GIDs.
* Patch 3 'extracts' the OPA extended LIDs from the GID fields when
handling the connection request
Please note that these patches apply on top of the previously submmitted
patch set with subject: "[PATCH rdma-next 0/8] Add OPA extended LID support"
Dasaratharaman Chandramouli (2):
IB/CM: Create appropriate path records when handling CM request
IB/CM: Set appropriate slid and dlid when handling CM request
Don Hiatt (1):
IB/CM: Add OPA Path record support to CM
drivers/infiniband/core/cm.c | 155 +++++++++++++++++++++++++++++++++++--------
include/rdma/opa_addr.h | 18 +++++
2 files changed, 147 insertions(+), 26 deletions(-)
--
1.8.3.1
--
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 reply other threads:[~2017-06-08 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 17:38 Don Hiatt [this message]
[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 ` [PATCH rdma-next v3 0/3] Enhance IB CM to support OPA extended LIDs Doug Ledford
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=1496943484-44065-1-git-send-email-don.hiatt@intel.com \
--to=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