Tom Tucker wrote:
Its OK to call rdma_reject on active side as well, isn't it?
You'll get -EINVAL on iWARP if you do this
For IB, rdma_reject can be called on the active side if the user is managing
their own QP states, or is SDP. How does iWarp support userspace QPs?
- Sean
Quoting r. Sean Hefty [EMAIL PROTECTED]:
Subject: Re: [openib-general] rdma_cm.h: comment nits.
Tom Tucker wrote:
Its OK to call rdma_reject on active side as well, isn't it?
You'll get -EINVAL on iWARP if you do this
For IB, rdma_reject can be called on the active side if the user
Michael S. Tsirkin wrote:
BTW, Sean, could you please explain why is RESPONSE event IB-specific?
Does not it match Syn/Ack in the TCP 3-way handshake?
I didn't think that even iWarp exposed the TCP connection messages to the users.
Plus iWarp connections can be formed over an existing TCP
[EMAIL PROTECTED] wrote:
Tom Tucker wrote:
Its OK to call rdma_reject on active side as well, isn't it?
You'll get -EINVAL on iWARP if you do this
For IB, rdma_reject can be called on the active side if the
user is managing their own QP states, or is SDP. How does iWarp
support
On Wed, 2006-05-10 at 09:26 -0700, Sean Hefty wrote:
Tom Tucker wrote:
Its OK to call rdma_reject on active side as well, isn't it?
You'll get -EINVAL on iWARP if you do this
For IB, rdma_reject can be called on the active side if the user is managing
their own QP states, or is
Tom Tucker wrote:
So... all that said, I could in fact support rdma_reject on
an active side connection. But this would effectively reduce
to a QP -- ERROR and I doubt this matches the semantics
you're looking for.
And you could send an RST. There's just no way to send any user
On Wed, 2006-05-10 at 14:20 -0700, Caitlin Bestler wrote:
Tom Tucker wrote:
So... all that said, I could in fact support rdma_reject on
an active side connection. But this would effectively reduce
to a QP -- ERROR and I doubt this matches the semantics
you're looking for.
On Mon, 2006-05-08 at 16:58 +0300, Michael S. Tsirkin wrote:
Two nits wrt rdma_cm.h:
/**
* * rdma_reject - Called on the passive side to reject a connection request.
*/
Its OK to call rdma_reject on active side as well, isn't it?
You'll get -EINVAL on iWARP if you do this
/**
Michael S. Tsirkin wrote:
Two nits wrt rdma_cm.h:
/**
* * rdma_reject - Called on the passive side to reject a connection request.
*/
Its OK to call rdma_reject on active side as well, isn't it?
Yes - but only for users that are managing the QP states themselves.
/**
*
