Questions about MSI limits in GoInterruptPolicy

Everything about latency. This section is mainly user/consumer discussion. (Peer-reviewed scientific discussion should go in Laboratory section). Tips, mouse lag, display lag, game engine lag, network lag, whole input lag chain, VSYNC OFF vs VSYNC ON, and more! Input Lag Articles on Blur Busters.
Post Reply
dermodemon
Posts: 181
Joined: 10 Aug 2023, 12:03

Questions about MSI limits in GoInterruptPolicy

Post by dermodemon » 23 Apr 2025, 06:34

1. What are those MSI limit parameters and what are they doing?
2. Can i go higher than a default MSI limit (my XHCI limit is 8, what will happen when i set it to 32 for example)?
3. Why my gpu msi limit is only 1 and XHCI for example is 8?
Image

User avatar
kyube
Posts: 1037
Joined: 29 Jan 2018, 12:03

Re: Questions about MSI limits in GoInterruptPolicy

Post by kyube » 23 Apr 2025, 11:47

dermodemon wrote: ↑
23 Apr 2025, 06:34
1. What are those MSI limit parameters and what are they doing?
2. Can i go higher than a default MSI limit (my XHCI limit is 8, what will happen when i set it to 32 for example)?
3. Why my gpu msi limit is only 1 and XHCI for example is 8?
https://docs.kernel.org/PCI/msi-howto.html
https://forums.guru3d.com/threads/windo ... ol.378044/
These two threads might help you understand
https://calypto.us
https://github.com/valleyofdoom/PC-Tuning

I would advise against doing any modification to the driver default MSI limit, this is something done on a driver software level and it can lead to issues if you change it.
Instead, consider trying to change the core (default is Core 0 for all drivers) in which the DPC/ISR's are being executed.
This can lead to benefits.

KrendeLь
Posts: 6
Joined: 29 Apr 2025, 13:35

Re: Questions about MSI limits in GoInterruptPolicy

Post by KrendeLь » 15 May 2025, 17:34

kyube wrote: ↑
23 Apr 2025, 11:47

I would advise against doing any modification to the driver default MSI limit, this is something done on a driver software level and it can lead to issues if you change it.
Instead, consider trying to change the core (default is Core 0 for all drivers) in which the DPC/ISR's are being executed.
This can lead to benefits.
Which drivers can be bound to the kernel and which ones should not be touched to avoid a BSOD?

Post Reply