We talked about this on the weekly call today. Conclusions:
1. Looks like we just goofed on the CQ default size values. Doh!
2. There does not appear to be any reason we're not using the device CQ max
size by default. Ticket #3152 changes the trunk to do this (and we'll CMR to
v1.6 and v1.7).
If I use --mca btl_oepnib_cq_size and override the computed CQ depth,
then I can indeed avoid the CQ overflows.
On 7/2/2012 4:12 PM, Jeff Squyres wrote:
You know, I have the following in a few of my MTT configurations:
-
# See if this makes the CQ overrun errors go away
cq_depth = " --mca
You know, I have the following in a few of my MTT configurations:
-
# See if this makes the CQ overrun errors go away
cq_depth = " --mca btl_openib_cq_size 65536 "
-
And then I use that variable as an mpirun CLI option in a few places. It looks
like someth
Hello,
I'm debugging an issue with openmpi-1.4.5 and the openib btl over
chelsio iwarp devices. I am the iwarp driver developer for this
device. I have debug code that detects cq overflows, and I'm seeing rcq
overflows during finalize for certain IMB runs with ompi.So as the
recv wrs a
