Pieter Noordhuis

I'll try to wrap something up when I have the time.

@EnricoMi I don't work on Gloo anymore. The change looks good to me though :-)

Hey, thanks for opening the issue. I mentioned in our conversation earlier that we would have to make Gloo pick use predefined ports such that you can whitelist them in...

You could start in `Pair::listen`, that's where the `bind(2)` function is called ([link](https://github.com/facebookincubator/gloo/blob/master/gloo/transport/tcp/pair.cc#L130)). You could choose to use for example 8 ports round robin if your context is not larger...

@erikwijmans Currently it still lets the OS pick a port to bind to. It is technically possible to force a range of ports on the listening side, as long as...

It lets the operating system decide which port to use. AFAIK this means it picks an unused port from the ephemeral port range. You can get/set this range with `sysctl`...

Fixing a few bugs...

@Hiroki11x Making a proper fix for this is still on the back burner. In the mean time you can compile with NCCL support and everything will work out of the...

@jithunnair-amd Checking in internally on how to proceed.

@jithunnair-amd We still require a CLA for repo's outside the `pytorch` org. I think AMD already has one, so it should be possible to whitelist. Can you check on your...