Hal Rosenstock wrote:
On Fri, Feb 5, 2010 at 9:18 AM, Eli Dorfman dorfman@gmail.com wrote:
On Thu, Feb 4, 2010 at 10:52 PM, Hal Rosenstock
hal.rosenst...@gmail.com wrote:
On Thu, Feb 4, 2010 at 12:43 PM, Eli Dorfman (Voltaire)
dorfman@gmail.com wrote:
Subject: [PATCH] Wrong handling
On 2/7/2010 3:22 AM, Steve Wise wrote:
Good catch, I'll update the patch and submit for 2.6.33 on Monday.
NOTE: This doesn't solve our IB/openmpi regression for ofed-1.5.1.
If this patch will be accepted to the kernel 2.6.33 we can take it too
Tziporet
--
To unsubscribe
Vladislav Bolkhovitin wrote:
Or Gerlitz wrote:
From where did you get those latency numbers?
read iostat(8), you'll see that await is The average time (in milliseconds)
for I/O requests issued to the device to be served
what kind of test did you do?
I connected a Linux box through iser to
Tziporet Koren wrote:
On 2/7/2010 3:22 AM, Steve Wise wrote:
Good catch, I'll update the patch and submit for 2.6.33 on Monday.
NOTE: This doesn't solve our IB/openmpi regression for ofed-1.5.1.
If this patch will be accepted to the kernel 2.6.33 we can take it too
If
My point, though, is that even with this patch in ofed-1.5.1, we still
have an openmpi/IB/rdmacm regression. The only way to avoid this
regression without changing openmpi is to disallow _all_ rdma binds to
127.0.0.1.
Can you identify the source of the regression? ie what was the change
Roland Dreier wrote:
My point, though, is that even with this patch in ofed-1.5.1, we still
have an openmpi/IB/rdmacm regression. The only way to avoid this
regression without changing openmpi is to disallow _all_ rdma binds to
127.0.0.1.
Can you identify the source of the regression?
Can you identify the source of the regression? ie what was the change
that broke things?
My understanding is that support for loopback addresses exposes an existing bug
in openmpi. It tries to bind to 127.0.0.1, which now succeeds. Openmpi passes
that address to a remote node for use in
Since iWarp devices are not guaranteed to support loopback connections,
prevent rdma_bind_addr from associating the loopback address with
an iWarp device.
Signed-off-by: Sean Hefty sean.he...@intel.com
---
This includes feedback from Steve Wise based on the initial rfc patch.
Although this patch
