RE: [Ipoverib] Comments on IPoIB Connected Mode Connection Establ ishment
Dror Goldenberg <gdror@mellanox.co.il> Sun, 21 August 2005 06:38 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E6jTR-0006Nw-IW; Sun, 21 Aug 2005 02:38:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E6jTL-0006NH-HI for ipoverib@megatron.ietf.org; Sun, 21 Aug 2005 02:38:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10245 for <ipoverib@ietf.org>; Sun, 21 Aug 2005 02:38:21 -0400 (EDT)
Received: from [194.90.237.34] (helo=mtlex01.yok.mtl.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E6k3b-0000vY-Rn for ipoverib@ietf.org; Sun, 21 Aug 2005 03:15:54 -0400
Received: by mtlex01.yok.mtl.com with Internet Mail Service (5.5.2653.19) id <RC513D6P>; Sun, 21 Aug 2005 09:37:40 +0300
Message-ID: <506C3D7B14CDD411A52C00025558DED60893A24D@mtlex01.yok.mtl.com>
From: Dror Goldenberg <gdror@mellanox.co.il>
To: Vivek Kashyap <kashyapv@us.ibm.com>, Dror Goldenberg <gdror@mellanox.co.il>
Subject: RE: [Ipoverib] Comments on IPoIB Connected Mode Connection Establ ishment
Date: Sun, 21 Aug 2005 09:37:37 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: IPoverIB <ipoverib@ietf.org>
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>, <mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>, <mailto:ipoverib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1242331108=="
Sender: ipoverib-bounces@ietf.org
Errors-To: ipoverib-bounces@ietf.org
> From: Vivek Kashyap [mailto:kashyapv@us.ibm.com] > Sent: Thursday, August 18, 2005 9:36 AM > > On Wed, 17 Aug 2005, Dror Goldenberg wrote: > > > > > > >> From: Vivek Kashyap [mailto:kashyapv@us.ibm.com] > >> Sent: Monday, August 15, 2005 9:41 AM > >> > >> On Wed, 10 Aug 2005, Dror Goldenberg wrote: <snip> > > >>> (2) Active/Active Model Support > >>> <snip> > >> 3. In case of the active-active connection the request from the > >> numerically smaller MAC Address (QPN+GID or probably just > the GID) is > >> terminated. The error code 'state connection' is a > possibility here. > >> > >> The active-active situation is known when it is determined > that there > >> is an outstanding request to the remote peer (as determined by > >> GID+QPN) while a request from the same is received on local > >> GID+ServiceID. > > > > In IB, active-active is only determined by equal Service IDs. See IB > > spec 1.2 vol1 12.9.7.1, the Active CM state machine goes to > > Peer-Compare state based solely on the Service ID. > > Therefore, if you want to have active-active, then you must > ensure that > > both service IDs are identical. In the current draft, the > Service IDs are > > different, as they include a remote QP number. > > > > Yes, if we are determining it based on the CM. However, I was > suggesting > the above as what the ipoib component will do when it is informed by > CM. It can return a suitable error to CM when it determines > that a particular > connection shouldn't be allowed. Is that not possible? > That wouldn't be "active/active" per se. But maybe it's just as good, because it just pushes this model to the ipoib layer. In a case of crossing connection requests one side is supposed to accept, while the other is supposed to reject. The rules for rejection have to be described in the RFC. Maybe it worth describing the state machine that now needs to be implemented in ipoib. BTW, what will be the rejection reason ? Seems like the most appropriate is 28 - consumer reject. Note that it becomes tricky if you want to allow more than one connection on the same service ID. So, is there a way you can tell whether your peer is trying to establish the 1st or 2nd connection while you are trying to set up the 1st one ? I think it'll be best if we can use the standard active-active mechanism. However, if we don't manage to find how, then this approach (rejection at the app level) will do the work. However, it will complicate the ipoib implementation and will duplicate the active-active work that is already implemented in the cm. -Dror <snip>
_______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib
- RE: [Ipoverib] Comments on IPoIB Connected Mode C… Dror Goldenberg
- RE: [Ipoverib] Comments on IPoIB Connected Mode C… Vivek Kashyap
- Re: [Ipoverib] Comments on IPoIB Connected Mode C… Vivek Kashyap
- RE: [Ipoverib] Comments on IPoIB Connected Mode C… Dror Goldenberg
- RE: [Ipoverib] Comments on IPoIB Connected Mode C… Vivek Kashyap
- RE: [Ipoverib] Comments on IPoIB Connected Mode C… Dror Goldenberg
- RE: [Ipoverib] Comments on IPoIB Connected Mode C… Michael Krause
- RE: [Ipoverib] Comments on IPoIB Connected Mode C… Vivek Kashyap