From: "Ted H. Kim" <ted.h.kim-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "Hefty,
Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] ib/cm: Change reject message type when destroying cm_id
Date: Mon, 18 May 2015 14:27:51 -0700 [thread overview]
Message-ID: <555A5957.7080508@oracle.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373A8FDBF8D-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 05/15/15 10:06 AM, Hefty, Sean wrote:
>> Did you intend to add an ISSUE B: section to the commit message?
>
> The issue is listed as the missing comm id. Though, thinking about it
> again, the issue may have been a missing node GUID. I can't recall now.
> Maybe Ted does.
Imagine the case of the Linux active side sending REQ with it's CM communication
id. When it gets the REP back, the other side's communication ID
will be received and internal CM state updated. So any REJ from this
point on can send both communication IDs.
Now imagine a slightly different case. The active side sends the REQ,
and the passive side responds with MRA. At this point the CM should
update the state with the second communication ID coming in the
MRA. But it does not do so. This is "ISSUE B". This is will require
a different fix from the patch in question to add the communication ID
updating when getting an MRA.
So as a side effect, a REJ issued at this point by the active side
has only its own communication ID. The problem with only one communication ID
REJs is that they are all generated by remote systems from the one being
sent the REJ and therefore might not be unique. The way that TIMEOUT
REJ addresses this is to have a GUID in the ARI to make it unique.
But other REJ codes don't have this.
-ted
> The IB spec is goofy here in that it only allows a CM REQ, once sent,
> to timeout. It doesn't define an 'abort' case. The spec also treats
> the connection is being in a single 'REP wait' state, regardless of
> whether an MRA has been received or not. This change results in
> the 'I got an MRA but I'm waiting for a REP' to be handled the
> same as 'I'm waiting for a REP', at least for the destruction case.
--
Ted H. Kim, PhD
Sun/Oracle America ted.h.kim-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org
5750 Hannum Drive, #200 +1 310-258-7536
Culver City, CA 90230
--
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-05-18 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 19:49 [PATCH] ib/cm: Change reject message type when destroying cm_id sean.hefty-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1431632941-3430-1-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-05-15 16:40 ` Doug Ledford
[not found] ` <1431708034.29187.14.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-15 17:06 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373A8FDBF8D-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-05-18 21:27 ` Ted H. Kim [this message]
2015-05-19 18:14 ` Jason Gunthorpe
[not found] ` <20150519181457.GD18675-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-05-19 18:25 ` Hefty, Sean
2015-05-18 15:04 ` 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=555A5957.7080508@oracle.com \
--to=ted.h.kim-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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