The type of the second argument to the MTHCA_PUT() macro determines how
many bytes will be written to inbox. Judging from the context, the
current code is doing the right thing by writing an int of data. But I
would feel more comfortable making it explicit that we are writing 32
bits.
This is
On 8/14/2013 6:26 AM, Line Holen wrote:
Signed-off-by: Line Holen line.ho...@oracle.com
---
diff --git a/opensm/osm_port_info_rcv.c b/opensm/osm_port_info_rcv.c
index 7dcd15e..961b376 100644
--- a/opensm/osm_port_info_rcv.c
+++ b/opensm/osm_port_info_rcv.c
@@ -85,7 +85,7 @@ static void
@@ -884,6 +884,13 @@ int main(int argc, char *argv[])
if (ctx.use_event)
ibv_ack_cq_events(ctx.recv_cq, num_cq_events);
+ /* Process should wait before closing its resources to make sure
+ * latest daemon's response sent via its target QP destined to an XSRQ
+
From: Alex Netes ale...@mellanox.com
For base switch port 0, these values aren't defined/used.
Signed-off-by: Alex Netes ale...@mellanox.com
Signed-off-by: Hal Rosenstock h...@mellanox.com
---
opensm/osm_lid_mgr.c | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git
I am looking at a multithreaded application here, and I believe that
the race is between thread A calling the rpoll() for POLLIN event and
thread B calling the shutdown(SHUT_RDWR) for reading and writing of
the (r)socket almost immediately afterwards.
I modified a test program, and I can