Thomas Gillis

@yosefe thanks a lot for the very quick answer! I have just submitted with `UCX_TLS=^xpmem`. I would love to update to the latest version but unfortunately I am a limited...

> In meantime, let's understand how UCX_TLS affects the error message: it's unexpected that when setting `UCX_TLS=dc_mlx5` or `UCX_TLS=ud_mlx5` we would still see errors from xpmem. Is this really the...

> @dmitrygx good catch! i guess we should just ignore 0-size regions and create some kind of dummy rkey for them As a hack I can allocate a bit of...

@yosefe I get this weird error message with `export UCX_TLS=^xpmem,dc_mlx5,sm,self`: ``` UCX WARN transport '^xpmem' is not available, please use one or more of: cma, dc, dc_mlx5, dc_x, ib, mm,...

> > > @dmitrygx good catch! i guess we should just ignore 0-size regions and create some kind of dummy rkey for them > > > > > > As...

yes, I think so (but the Cray modules are such a maze that I am not entirely sure): ``` MPICH Version: 3.4a2 MPICH Release date: unreleased development copy MPICH Device:...

@yosefe @dmitrygx I looks like the runs with `UCX_TLS=dc,self,posix,sysv,cma` could complete normally. So I presume that the `xpmem` is the cause of the issue (it's not open-source right?) For the...

> The version of XPMEM used by Cray is not exactly the same version as open source, which is based on some older revision of Cray version. @yosefe is the...

@dmitrygx okay will try. What is the best way to know what version of UCX is taken by MPICH? is there any verbose variable I can use?

Old list and needs to be ignored. > ## Review checklist for @thomasgillis > > ### Conflict of interest > > - [x] I confirm that I have read the...