aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-aws (Ubuntu) |
Fix Released
|
Undecided
|
Philip Cox | ||
Focal |
Fix Released
|
Undecided
|
Philip Cox | ||
Jammy |
Fix Released
|
Undecided
|
Philip Cox | ||
Mantic |
Fix Released
|
Undecided
|
Philip Cox | ||
Noble |
Fix Released
|
Undecided
|
Philip Cox |
Bug Description
SRU Justification:
[Impact]
In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our latest generation instances with networking heavy workloads is up to a 25% performance regression (i.e. NGINX in a load-balancing configuration).
[Fix]
The mainline Linux kernel will now support IRQ moderation by default for ENA in the 6.9 kernel release via this patch: https:/
[Test Plan]
AWS tested
[Where problems could occur]
By enabling adaptive coalescing, the default interrupt behaviour will by changed to be more adaptive, which shows improvements on heavy network workloads, but my change the behaviour and performance on other network workloads differently. Rather than handling the interrupts based off of a fixed amount of time elapsed, it will change to an adaptive based approach. There should be no negative impact on light workloads, and a positive impact on heavy work loads. If there is an impact though, this option can be disabled via the ethtool command.
[Other Info]
SF: 00380449
Changed in linux-aws (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in linux-aws (Ubuntu Mantic): | |
status: | New → In Progress |
Changed in linux-aws (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux-aws (Ubuntu Noble): | |
status: | New → In Progress |
Changed in linux-aws (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-aws (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-aws (Ubuntu Mantic): | |
status: | In Progress → Fix Committed |
Changed in linux-aws (Ubuntu Noble): | |
status: | In Progress → Fix Committed |
Changed in linux-aws (Ubuntu Focal): | |
assignee: | nobody → Philip Cox (philcox) |
Changed in linux-aws (Ubuntu Jammy): | |
assignee: | nobody → Philip Cox (philcox) |
Changed in linux-aws (Ubuntu Mantic): | |
assignee: | nobody → Philip Cox (philcox) |
tags: |
added: verification-passed-focal-linux-aws verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux-aws removed: verification-needed-focal-linux-aws verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws-fips verification-needed-mantic-linux-aws |
tags: |
added: verification-done-focal-linux-aws verification-done-focal-linux-aws-5.15 verification-done-jammy-linux-aws-fips verification-done-mantic-linux-aws removed: verification-passed-focal-linux-aws verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux-aws |
This bug is awaiting verification that the linux-aws/ 5.4.0-1122. 132 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- focal-linux- aws' to 'verification- done-focal- linux-aws' . If the problem still exists, change the tag 'verification- needed- focal-linux- aws' to 'verification- failed- focal-linux- aws'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!