Thanks Josh for the extended checks, I have tagged it up for Bionic correctly and sponsored it for the review of the SRU [1] Team. Once they accept it into Bionic-proposed they will ask for a verification, it would be great if you again could check then that it works. It could, but doesn't necessarily be the full check, but at least if the device recognition that was planned to be fixed really works with that build (of the same source) still.
[1]: https://wiki.ubuntu.com/StableReleaseUpdates ** Also affects: rdma-core (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: rdma-core (Ubuntu Bionic) Status: New => Triaged ** Changed in: rdma-core (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: rdma-core (Ubuntu) Status: Triaged => Fix Released ** Description changed: [Impact] - * Azure RDMA devices can be a "Network Direct" version of the MLX - InfiniBand card that is exposed to the guest and they need to be - handled by the MLX4 driver. + * Azure RDMA devices can be a "Network Direct" version of the MLX + InfiniBand card that is exposed to the guest and they need to be + handled by the MLX4 driver. But to be enabled properly the system needs to detect them as such. That was added in rdma-core v20 hence being fix released in >=Disco. * Fix [1] is just a new alias to detect the card as what it is. [Test Case] - * TBD: Try to use rdma on "Microsoft Azure RDMA device". - It would be great if someone could add some real content here. + * The TL;DR is to use rdma on "Microsoft Azure RDMA device". + There is no good way without an Azure instance to test this specific + bug. The check is if the userspace drivers are then correctly loaded. + Lacking such an instance myself Microsoft helped on the PPA and will + help on SRU verification. [Regression Potential] * a) The regression potential should be minimal. Existing systems either already match the HCA table or they don't (neither before nor after the fix. An issue I could think of is if there are devices that announce as vmbus:3daf2e8ca732094bab99bd1f1c86b501 but are NOT in fact this device type - they would then run into issues. * b) Of course the fix will "enable rdma support on some more devices" if someone had those devices attached but didn't use/configure them they might now initialize a bit further. But that isn't an issue and especially in cloud environments where HW config is just a click away no one usually pays for extra devices without using them. * c) I happen to know that for DPDK usage of these devices several fixes in later rdma-core are preferred or even needed. I'm not sure about the usage in this case - but enabling could expose those issues which formerly were hidden behind the "not supported" misdetection of the card. For B) and C) I'd want Microsoft to ack and test this from a PPA and do the verification on this - to be not only ok for this but for for Azure in general. [Other Info] * This falls under the SRU exception of "other safe cases" for "For Long Term Support releases we regularly want to enable new hardware". New modaliases are explicitly listed there as cases for this. - * This is reported to work in 16.04, but not as a classic "this commit - broke it regression". Back then the world of rdma/infiniband just - worked totally different as it was before the big revamp into rdma-core - never the less one could see that (abstract, not caring about details) - as an update-regression when going 16.04 to 18.04. + * This is reported to work in 16.04, but not as a classic "this commit + broke it regression". Back then the world of rdma/infiniband just + worked totally different as it was before the big revamp into rdma-core + never the less one could see that (abstract, not caring about details) + as an update-regression when going 16.04 to 18.04. [1]: https://github.com/linux-rdma/rdma- core/commit/b98397f3068a42e7d8e67d4ef2a90393b4c4f08a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838939 Title: Add alias to support Microsoft Azure RDMA device via MLX4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1838939/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
