New
#1
interrupt affinity, system handles interrupts only on core0
I have everything in msi/msi-x mode, except usb. From measuring dpc in latencymon, i have still 400k dpc calls on core 0, while other 7 cores gets 500-7000 for each, which is disappointing.
And setting in regedit interrupt affinity doesn't help, because hardware/drivers can override that setting. It is really strange, that hardware/drivers/windows wouldn't allocate multicore for handling interrupts: my pc isn't that old i have i7 3700k chipset b75m, which isn't best but still... Interrupts should be spread on all cores, instead being handled only on core 0. It is really like something from 2005.
I am positive i have set it under right device in regedit and i entered under Affinity Policy: "DevicePolicy" and put value 3 in decimal. Or i tried put there IrqPolicyAllProcessorsInMachine instead devicepolicy. Because i am unsure if i have to put there either this or that. But again drivers/hardware can override this setting, so it hasn't necessarily have to work.
https://technet.microsoft.com/en-us/ff547969(v=vs.96)
Still i would expect hardware and drivers should handle this and use multicore for interrupts today times. I am getting new pc, so i will test it on that and hopefully it will be fine. But this doesn't make sense...
Edit: after setting device/driver to msi, interrupt affinity started to work, which shouldn't be needed for it to work.
Last edited by empleat; 13 Dec 2019 at 16:46.