[EMAIL PROTECTED] wrote:
Tom Tucker wrote:
I think this makes sense for IB, however, for TCP based transports,
we should share the port space with TCP.
My view is that the iWarp transport needs to provide the
mapping from an RDMA_PS_TCP to the actual TCP port space,
RDMA_PS_UDP to UDP,
[EMAIL PROTECTED] wrote on Wed, 09 Aug 2006 14:07 -0700:
Pete Wyckoff wrote:
Calling rdma_listen() on a cm_id bound to INADDR_ANY can fail, e.g.
with EADDRINUSE, but report no error back to the user. This patch
fixes that by propagating the error. Success occurs only if at
least one of the
Pete Wyckoff wrote:
1) When a device gets added to the system, is there code that applies
existing INADDR_ANY listens to the new device? Where?
Yes - see cma_add_one() where cma_listen_on_dev() is called.
By the way, shouldn't the rdma_bind_addr call that preceeded
rdma_listen have failed
On Wed, 2006-08-16 at 14:29 -0700, Sean Hefty wrote:
Pete Wyckoff wrote:
1) When a device gets added to the system, is there code that applies
existing INADDR_ANY listens to the new device? Where?
Yes - see cma_add_one() where cma_listen_on_dev() is called.
By the way, shouldn't the
Tom Tucker wrote:
I think this makes sense for IB, however, for TCP based transports, we
should share the port space with TCP.
My view is that the iWarp transport needs to provide the mapping from an
RDMA_PS_TCP to the actual TCP port space, RDMA_PS_UDP to UDP, etc. This is a
function that
On Wed, 2006-08-09 at 14:07 -0700, Sean Hefty wrote:
Pete Wyckoff wrote:
Calling rdma_listen() on a cm_id bound to INADDR_ANY can fail, e.g.
with EADDRINUSE, but report no error back to the user. This patch
fixes that by propagating the error. Success occurs only if at
least one of the
Sorry, Sean, I can't spell today
On Sun, 2006-08-13 at 15:22 -0500, Tom Tucker wrote:
On Wed, 2006-08-09 at 14:07 -0700, Sean Hefty wrote:
Pete Wyckoff wrote:
Calling rdma_listen() on a cm_id bound to INADDR_ANY can fail, e.g.
with EADDRINUSE, but report no error back to the user.
Pete Wyckoff wrote:
Calling rdma_listen() on a cm_id bound to INADDR_ANY can fail, e.g.
with EADDRINUSE, but report no error back to the user. This patch
fixes that by propagating the error. Success occurs only if at
least one of the possibly multiple devices in the system was able to
Calling rdma_listen() on a cm_id bound to INADDR_ANY can fail, e.g.
with EADDRINUSE, but report no error back to the user. This patch
fixes that by propagating the error. Success occurs only if at
least one of the possibly multiple devices in the system was able to
listen. In the case of
