5 ms·
OTOH, why should we want an Infiniband monoculture (which is also a Mellanox/Nvidia monopoly)? Why not let AWS try their weird stuff and let it fail on its meri
by wmf 6y ago
OTOH, why should we want an Infiniband monoculture (which is also a Mellanox/Nvidia monopoly)? Why not let AWS try their weird stuff and let it fail on its merits?
- stonogo 6y agoBreaking the infiniband monoculture is why I am sad they're sitting on this protocol. I would like to deploy it to my cluster in my datacenter for testing. I cannot, and that sucks. Even if SRD is the greatest thing ever, it doesn't do me any good to replace an infiniband monoculture with an AWS monopoly. I can't even use public-cloud computing for about two thirds of my workload, so this is a non-starter.
- wmf 6y agoEven if the protocol was documented you couldn't use it without hardware which AWS won't sell you.
- stonogo 6y agoWe'll never know. I have access to network hardware that is extremely configurable via FPGA. "What hardware does this protocol require for successful deployment" is just one of the many questions that are currently only answerable via Amazon trademarks.
- wmf 6y agoI have a feeling that anyone competent enough to implement SRD in an FPGA could also invent their own similar protocol.
- stonogo 6y agoThat may be true, but I'm not funded to develop similar protocols. I am funded to evaluate them, which, again, I cannot do because of how they're handling this work.
- gnufx 6y agoI agree on monoculture, the point is it does appear to fail (and the Cisco usNIC offering looked better). There are alternative HPC fabrics in new hardware: OPA (although being canned by Intel), Shasta (Cray), BXI (Bull), and Tofu (Fujitsu), at least, and surely AWS could build their own if they wanted. I don't know whether Oracle still have their own IB, which might be in their cloud if you want to get involved with Oracle. Edit: Fix Cisco fabric name, add OPA.