Messages in this thread | | | From | Mikhail Gavrilov <> | Date | Tue, 6 Feb 2024 21:12:24 +0500 | Subject | Re: This is the fourth time I’ve tried to find wha t led to the regression of outgoing network speed and each t ime I find the merge commit 8c94ccc7cd691472461448f98e2372c7 5849406c |
| |
On Tue, Feb 6, 2024 at 4:24 PM Mathias Nyman <mathias.nyman@linux.intel.com> wrote: > > > This seems odd, not sure how this usb host change would impact your network speed. > > Could you try reverting that patch from 6.8-rc1 and see if it helps? > > There are some other patches on top of it that needs to be reverted first. > These should be enough: > > 36b24ebf9a04 xhci: minor coding style cleanup in 'xhci_try_enable_msi() > 9831960df237 xhci: rework 'xhci_try_enable_msi()' MSI and MSI-X setup code > dfbf4441f2d3 xhci: change 'msix_count' to encompass MSI or MSI-X vectors > a795f708b284 xhci: refactor static MSI function > 74554e9c2276 xhci: refactor static MSI-X function > f977f4c9301c xhci: add handler for only one interrupt line
I confirm after reverting all listed commits and 57e153dfd0e7 performance of the network returned to theoretical maximum.
> That patch changes how we request MSI/MSI-X interrupt(s) for xhci. > > Is there any change is /proc/interrupts between a good and bad case? > Such as xhci_hcd using MSI-X instead of MSI, or eth0 and xhci_hcd > interrupting on the same CPU?
On the good kernel I have - 32 xhci_hcd, and bad only - 4. In both scenarios using PCI-MSIX. I attached both interrupt output as archives to this message.
[1] https://postimg.cc/zL2RYgYZ
-- Best Regards, Mike Gavrilov. [unhandled content-type:application/zip][unhandled content-type:application/zip] | |