lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 27 Nov 2023 09:36:38 +0000
From: Souradeep Chakrabarti <>
To: Jakub Kicinski <>, Souradeep Chakrabarti
CC: KY Srinivasan <>, Haiyang Zhang <>,
	"" <>, Dexuan Cui <>,
	"" <>, ""
	<>, "" <>, Long Li
	<>, ""
	<>, "" <>,
	"" <>,
	"" <>,
	"" <>, ""
	<>, ""
	<>, ""
	<>, ""
	<>, ""
	<>, Paul Rosswurm <>
Subject: RE: [EXTERNAL] Re: [PATCH V2 net-next] net: mana: Assigning IRQ
 affinity on HT cores

>-----Original Message-----
>From: Jakub Kicinski <>
>Sent: Wednesday, November 22, 2023 5:19 AM
>To: Souradeep Chakrabarti <>
>Cc: KY Srinivasan <>; Haiyang Zhang
><>;; Dexuan Cui
>; Long Li <>;
>;;; linux-
>; Souradeep Chakrabarti
><>; Paul Rosswurm <>
>Subject: [EXTERNAL] Re: [PATCH V2 net-next] net: mana: Assigning IRQ affinity on
>HT cores
>On Tue, 21 Nov 2023 05:54:37 -0800 Souradeep Chakrabarti wrote:
>> Existing MANA design assigns IRQ to every CPUs, including sibling
>> hyper-threads in a core. This causes multiple IRQs to work on same CPU
>> and may reduce the network performance with RSS.
>> Improve the performance by adhering the configuration for RSS, which
>> assigns IRQ on HT cores.
>Drivers should not have to carry 120 LoC for something as basic as spreading IRQs.
>Please take a look at include/linux/topology.h and if there's nothing that fits your
>needs there - add it. That way other drivers can reuse it.
Because of the current design idea, it is easier to keep things inside
the mana driver code here. As the idea of IRQ distribution here is :
1)Loop through interrupts to assign CPU
2)Find non sibling online CPU from local NUMA and assign the IRQs
on them.
3)If number of IRQs is more than number of non-sibling CPU in that
NUMA node, then assign on sibling CPU of that node.
4)Keep doing it till all the online CPUs are used or no more IRQs.
5)If all CPUs in that node are used, goto next NUMA node with CPU.
Keep doing 2 and 3.
6) If all CPUs in all NUMA nodes are used, but still there are IRQs
then wrap over from first local NUMA node and continue
doing 2, 3 4 till all IRQs are assigned.

Powered by blists - more mailing lists