RE: rdma_create_qp() and max_send_wr

2011-04-22 Thread Yann Droneaud
Hi, Le jeudi 21 avril 2011 à 11:53 -0700, c...@asomi.com a écrit : An ENOMEM return does not mean that the subsystem *just* failed to allocate system memory. The memory that could not be allocated could be device memory. I'm also having some difficulties with system memory

RE: rdma_create_qp() and max_send_wr

2011-04-22 Thread Yann Droneaud
And I forgot to mention: Le vendredi 22 avril 2011 à 12:20 +0200, Yann Droneaud a écrit : I'm also having some difficulties with system memory allocation. In this case of failure, strace shows the last write() syscall returning ENOMEM. Regards. -- Yann Droneaud OPTEYA -- To unsubscribe

opensm: file routing engine

2011-04-22 Thread Paul Monday (Parallel Scientific)
I've been toying with the file routing engine implementation for some work I'm doing, but I'm finding very little documentation on it. I only have one switch to experiment with at the moment as well so some of the information in the lid / lfts files that are generated are not obvious for how

[PATCH 1/2] RDMA/cxgb4: Reset wait condition atomically.

2011-04-22 Thread Steve Wise
The driver was never really waiting for RDMA_WR/FINI completions because the condition variable used to determine if the completion happened was never reset, and this condition variable is reused for both connection setup and teardown. This causes various driver crashes under heavy loads due to

[PATCH 2/2] RDMA/cxgb4: EEH errors can hang the driver.

2011-04-22 Thread Steve Wise
A few more EEH fixes: c4iw_wait_for_reply(): detect fatal EEH condition on timeout and return an error. The iw_cxgb4 driver was only calling ib_deregister_device() on an EEH event followed by a ib_register_device() when the device was reinitialized. However, the rdma core doesn't allow multiple

opensm: switch incorrectly reports IB_PORT_CAP_HAS_MCAST_FDB_TOP ?

2011-04-22 Thread Jim Schutt
Hi, I've been testing the current opensm development head (commit 83b67527d16 from git://git.openfabrics.org/~alexnetes/opensm), and I've been getting some messages that are new since version 3.3.7: Apr 22 12:08:09 646534 [411CD940] 0x01 - log_rcv_cb_error: ERR 3111: Received MAD with error

Re: opensm: file routing engine

2011-04-22 Thread Weiny, Ira K.
On Apr 22, 2011, at 7:41 AM, Paul Monday (Parallel Scientific) wrote: I've been toying with the file routing engine implementation for some work I'm doing, but I'm finding very little documentation on it. I only have one switch to experiment with at the moment as well so some of the

Re: opensm: switch incorrectly reports IB_PORT_CAP_HAS_MCAST_FDB_TOP ?

2011-04-22 Thread Weiny, Ira K.
On Apr 22, 2011, at 11:19 AM, Jim Schutt wrote: Hi, I've been testing the current opensm development head (commit 83b67527d16 from git://git.openfabrics.org/~alexnetes/opensm), and I've been getting some messages that are new since version 3.3.7: Apr 22 12:08:09 646534 [411CD940] 0x01 -

Re: opensm: switch incorrectly reports IB_PORT_CAP_HAS_MCAST_FDB_TOP ?

2011-04-22 Thread Hal Rosenstock
Hi Jim, On 4/22/2011 2:19 PM, Jim Schutt wrote: Hi, I've been testing the current opensm development head (commit 83b67527d16 from git://git.openfabrics.org/~alexnetes/opensm), and I've been getting some messages that are new since version 3.3.7: Apr 22 12:08:09 646534 [411CD940] 0x01 -

Re: opensm: switch incorrectly reports IB_PORT_CAP_HAS_MCAST_FDB_TOP ?

2011-04-22 Thread Jim Schutt
Weiny, Ira K. wrote: On Apr 22, 2011, at 11:19 AM, Jim Schutt wrote: Hi, I've been testing the current opensm development head (commit 83b67527d16 from git://git.openfabrics.org/~alexnetes/opensm), and I've been getting some messages that are new since version 3.3.7: Apr 22 12:08:09 646534

Re: opensm: file routing engine

2011-04-22 Thread Paul Monday (Parallel Scientific)
Thank you, your detail is greatly appreciated :) I have one other strange question ... is it possible to carve a single physical switch into two logical switches (put a cable between ports 16/17 and modify the routing tables ... this seems like it wouldn't work as the Unicast LID / Switch: guid

[PATCH] opensm: Provide option to disable use of MulticastFDBTop even if advertised

2011-04-22 Thread Hal Rosenstock
Default is on; as this is a workaround for non compliance: this feature is advertised but the SMA rejects sets of SwitchInfo that actually set MFTTop. Signed-off-by: Hal Rosenstock h...@mellanox.com --- diff --git a/include/opensm/osm_subnet.h b/include/opensm/osm_subnet.h index a9499dd..4bab8ee