Benjamin Brock
2018-09-26 18:25:46 UTC
In case anyone comes across this thread in an attempt to get RDMA over
Ethernet working on AWS, here's the conclusion I came to:
There are two kinds of NICs exposed to VMs on AWS:
- Intel 82599 VF
- This NIC is old and does not support RoCE or iWARP.
- It's a virtualized view of an actual Intel 82599 Ethernet Controller.
- On C3, C4, D2, I2, M4 (excluding m4.16xlarge), and R3 instances.
- Elastic Network Adapter (ENA)
- This is a virtual NIC without a RoCE or iWARP driver, and as far as I
can tell, does not have a RoCE or iWARP driver.
- I'm not sure which hardware NICs this is virtualizing, but without an
ENA RoCE driver, AWS VMs will not be able to use RoCE, regardless of
whether the hardware NIC supports it.
- On C5, C5d, F1, G3, H1, I3, m4.16xlarge, M5, M5d, P2, P3, R4, R5,
R5d, T3, X1, X1e, and z1d instances.
Ben
Ethernet working on AWS, here's the conclusion I came to:
There are two kinds of NICs exposed to VMs on AWS:
- Intel 82599 VF
- This NIC is old and does not support RoCE or iWARP.
- It's a virtualized view of an actual Intel 82599 Ethernet Controller.
- On C3, C4, D2, I2, M4 (excluding m4.16xlarge), and R3 instances.
- Elastic Network Adapter (ENA)
- This is a virtual NIC without a RoCE or iWARP driver, and as far as I
can tell, does not have a RoCE or iWARP driver.
- I'm not sure which hardware NICs this is virtualizing, but without an
ENA RoCE driver, AWS VMs will not be able to use RoCE, regardless of
whether the hardware NIC supports it.
- On C5, C5d, F1, G3, H1, I3, m4.16xlarge, M5, M5d, P2, P3, R4, R5,
R5d, T3, X1, X1e, and z1d instances.
Ben