Philip Davis

Is this a machine that has a PSM fabric? It might have two PSM interfaces and libfabric is using the wrong one. Would it be possible to get the output...

Apologies, I gave you the wrong flag. It should be ‘fi_info -t FI_EP_RDM’ (note the -t instead of -e) Sent from my mobile. > On Oct 8, 2021, at 5:09...

Yes, try the environment variables @eisen sent. If those don’t work, try setting FABRIiC_IFACE to mlx5_1 Sent from my mobile. > On Oct 8, 2021, at 5:29 PM, haiying xu...

Could you try exporting FI_PSM2_DISCONNECT=1 after the writer is started but before the reader starts? Sent from my mobile. > On Oct 8, 2021, at 6:13 PM, haiying xu ***@***.***>...

Are you installing with Spack, or manually? On Fri, Oct 8, 2021 at 9:06 PM haiying xu ***@***.***> wrote: > I checked the installation log of my libfabric, it looks...

In 1.12.0, you can individually disable the psm providers with --disable-psm --disable-psm2 --disable-psm3 Alternatively, you can set the environment variable FI_PROVIDER to verbs to limit the native providers libfabric will...

Yes, in the absence of some value in FABRIC_IFACE, SST is going to pick the first fabric interface that meets its constraints; it doesn't have the ability to do a...

You should be able to run the writer and/or reader on any number of available nodes. The only wrinkle might be if different ranks in the same MPI group need...

Is this Casper? If so, the way I have found to differentiate the interfaces is to look at the link_layer field. For example, in the following, mlx5_0 has a link_type...

Hello, `fi_pingpong` with those arguments is a good approximation, but there are few more constraints SST puts on libfabric that `fi_pingpong` doesn't. For a failure at init like you are...