Message ID | 20221028164959.1367250-1-vschneid@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | sched, net: NUMA-aware CPU spreading interface | expand |
On Fri, 28 Oct 2022 17:49:56 +0100 Valentin Schneider wrote: > Tariq pointed out in [1] that drivers allocating IRQ vectors would benefit > from having smarter NUMA-awareness (cpumask_local_spread() doesn't quite cut > it). > > The proposed interface involved an array of CPUs and a temporary cpumask, and > being my difficult self what I'm proposing here is an interface that doesn't > require any temporary storage other than some stack variables (at the cost of > one wild macro). > > [1]: https://lore.kernel.org/all/20220728191203.4055-1-tariqt@nvidia.com/ Not sure who's expected to take these, no preference here so: Acked-by: Jakub Kicinski <kuba@kernel.org> Thanks for ironing it out!
On 11/3/2022 4:56 AM, Jakub Kicinski wrote: > On Fri, 28 Oct 2022 17:49:56 +0100 Valentin Schneider wrote: >> Tariq pointed out in [1] that drivers allocating IRQ vectors would benefit >> from having smarter NUMA-awareness (cpumask_local_spread() doesn't quite cut >> it). >> >> The proposed interface involved an array of CPUs and a temporary cpumask, and >> being my difficult self what I'm proposing here is an interface that doesn't >> require any temporary storage other than some stack variables (at the cost of >> one wild macro). >> >> [1]: https://lore.kernel.org/all/20220728191203.4055-1-tariqt@nvidia.com/ > > Not sure who's expected to take these, no preference here so: > > Acked-by: Jakub Kicinski <kuba@kernel.org> > > Thanks for ironing it out! Thanks Jakub. Valentin, what do you think? Shouldn't it go through the sched branch?
On 08/11/22 13:25, Tariq Toukan wrote: > On 11/3/2022 4:56 AM, Jakub Kicinski wrote: >> On Fri, 28 Oct 2022 17:49:56 +0100 Valentin Schneider wrote: >>> Tariq pointed out in [1] that drivers allocating IRQ vectors would benefit >>> from having smarter NUMA-awareness (cpumask_local_spread() doesn't quite cut >>> it). >>> >>> The proposed interface involved an array of CPUs and a temporary cpumask, and >>> being my difficult self what I'm proposing here is an interface that doesn't >>> require any temporary storage other than some stack variables (at the cost of >>> one wild macro). >>> >>> [1]: https://lore.kernel.org/all/20220728191203.4055-1-tariqt@nvidia.com/ >> >> Not sure who's expected to take these, no preference here so: >> >> Acked-by: Jakub Kicinski <kuba@kernel.org> >> >> Thanks for ironing it out! > > Thanks Jakub. > > Valentin, what do you think? > Shouldn't it go through the sched branch? So yeah the topology bits should go through tip/sched/core, and given it's the only user of the new interface, the mlx5e one should probably be bundled with them.