> Both MVAPICH1 and MVAPICH2 have XRC support for many years and are being > used by many large-scale production clusters.
To clarify my comment: > > >> --with-rdma=gen2 CFLAGS='-DOFED_VERBS -D_ENABLE_XRC_ > > >> > > >> It didn't appear that mvapichs ever used XRC I only meant that mvapich2 didn't invoke any XRC calls in my testing. The portion of my patch which converted the ofed xrc calls to the new format weren't being tested, so this was a statement about my testing, not mvapich. > The runtime flag is VIADEV_USE_XRC > > Class: Run Time > Applicable device(s): Gen2 > When MVAPICH is compiled with the XRC CFLAGS, this parameter enables use > of the XRC transport of InfiniBand available on certain adapters. Enabling > XRC automatically enables Shared Receive Queue and on-demand connection > management. > > The hybrid (UD-RC/XRC) interface automatically selects the appropriate > interface at run time. > > Not sure which interface (gen2 or hybrid you are using). If you are using > the gen2 interface, looks like you are not using the correct runtime flag > to enable XRC with MVAPICH1. FYI - I was running in loopback on the same system. I'll try using the run time flag mentioned above if xrc can be used in that configuration (with shared memory disabled). Thanks. - Sean -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
