-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: XDP loading fails on amazon/RHEL-9.3.0_HVM-20240229-x86_64 #311
Comments
Small update, with the self-compiled driver we ended up at the following rejection now (which also confirms implicitly that ena on RHEL lacks some backports):
So it looks like the Are there plans to support XDP mbuf / multi-buffer for ena? Fwiw, that would lift the requirement to lower the MTU under XDP. |
Hi @borkmann Thank you for you inquiry. The message “Command parameter 46 is not supported” comes from the function ena_get_rxnfc() and is printed because currently the driver does not support flow steering. It is unrelated to xdp being able to load (as you saw when you compiled the github driver). If you don’t rely on flow steering you can probably ignore it. I tried loading xdp programs on RHEL 9 with your kernel and got an error (which may be different that what you see in dmesg), so indeed it seems there is an issue with xdp support in the driver that comes with this kernel. We will look into it, thank you for the heads up. It seems that your issue with this kernel may be different than what I see. It may be helpful if you could share with me:
I can’t answer your question whether it was fixed in upstream linux until I root cause your issue. But the issue I see myself was indeed fixed in upstream linux, and not backported yet to RHEL 9. Do I understand correctly that you are able to run your xdp program when using the latest github driver that you built yourself on RHEL 9? As for support for xdp multi-buffer for ena, this is currently under development, it will indeed lift the requirement to lower the MTU under XDP, but I can’t share here the timeline of release. Arthur |
Hi @borkmann, Another thing. 0001-Temporary-fix-for-XDP_REDIRECT-not-working-on-RHEL-9.patch Arthur |
Hi @borkmann, You've originally attached your dmesg when failing to load the xdp program up to :
Can you please share with me (here or via mail [email protected]) what happens in dmesg after that? Thanks! |
Hi @borkmann, |
Awesome, thanks so much! |
Cc'ing @strongjz . We've seen this in dmesg:
We basically weren't sure whether the command parameter 46 was related or not which was why we started asking in here. The error message related to XDP was lack of multi-buffer support for XDP. |
To make sure we are on the same page, I'm still not 100% sure what the issue you are seeing with the RHEL 9.3 preinstalled ENA driver that you don't see with the github driver. There are some known issues that are present up to RHEL 9.4, for which the bug fixes will be backported in RHEL 9.5 but from what you are saying I'm not sure you are experiencing them. Are you experiencing issues with the driver preinstalled in RHEL 9.3, that are not present in the github driver? What are they? Regarding your last message:
|
We've had two other folks run 9.3 default Ena driver fine. The 9.4 for me caused issues. I'm going to test next week with 9.3. |
@strongjz Can you please specify what you are running and what the issues are? |
Preliminary Actions
Driver Type
Linux kernel driver for Elastic Network Adapter (ENA)
Driver Tag/Commit
5.14.0-427.24.1.el9_4.x86_64
Custom Code
No
OS Platform and Distribution
amazon/RHEL-9.3.0_HVM-20240229-x86_64-27-Hourly2-GP3
And from dmesg:
Bug description
When trying to load our XDP program in Cilium on RHEL9.4, we're running into the following error in dmesg which seems correlated timing-wise:
And no XDP program got loaded on the device itself:
Is the ena driver regularly updated via HW enablement on RHEL9.x? We have users where self-building a driver before use would unfortunately not be an option for production.
We've seen somewhat related issues (#78, amzn/amzn-drivers#241) where this error might hint to XDP.
I hope this is still the right place to ask if it was fixed upstream, perhaps you have a chance to poke Red Hat folks to backport the relevant commits into RHEL9.
Reproduction steps
ip link set dev eth0 mtu 3498 ethtool -L eth0 combined 2 (we also tried with combined 1) load XDP
Expected Behavior
XDP program loads onto ena driver
Actual Behavior
[ 3037.066035] ena 0000:00:05.0 eth0: Command parameter 46 is not supported
Additional Data
No response
Relevant log output
No response
Contact Details
[email protected]
The text was updated successfully, but these errors were encountered: