On 4/14/21 12:11 PM, Jesse Brandeburg wrote: > Nitesh Narayan Lal wrote: > >>> The original issue as seen, was that if you rmmod/insmod a driver >>> *without* irqbalance running, the default irq mask is -1, which means >>> any CPU. The older kernels (this issue was patched in 2014) used to use >>> that affinity mask, but the value programmed into all the interrupt >>> registers "actual affinity" would end up delivering all interrupts to >>> CPU0, >> So does that mean the affinity mask for the IRQs was different wrt where >> the IRQs were actually delivered? >> Or, the affinity mask itself for the IRQs after rmmod, insmod was changed >> to 0 instead of -1? > The smp_affinity was 0xfff, and the kernel chooses which interrupt to > place the interrupt on, among any of the bits set.
I think what you are referring to here is the effective affinity mask. >From one of Thomas's commit message that you pointed me to: "The affinity mask is either the system-wide default or set by userspace, but the architecture can or even must reduce the mask to the effective set, which means that checking the affinity mask itself does not really tell about the actual target CPUs." I was looking into the code changes around IRQ and there has been major rework from Thomas in 2017. I recently tried testing the kernel just before those patches got merged. Specifically on top of 05161b9cbe5: x86/irq: Get rid of the 'first_system_vector' indirection bogosity On the box where I tested this, I was able to see the effective affinity being set to 0 (not SMP affinity) for several network device IRQs. and I think the reason for it is the usage of "cpumask_first_and(mask, cpu_online_mask)" in __assign_irq_vector(). But with the latest kernel, this has been replaced and that's why I didn't see the effective affinity being set to only 0 for all of the device IRQs. Having said that I am still not sure if I was able to mimic what you have seen in the past. But it looked similar to what you were explaining. What do you think? > > >> I did a quick test on top of 5.12.0-rc6 by comparing the i40e IRQ affinity >> mask before removing the kernel module and after doing rmmod+insmod >> and didn't find any difference. > with the patch in question removed? Sorry, I'm confused what you tried. Yeah, but I was only referring to the SMP affinity mask. Please see more up-to-date testing results above. >>> and if the machine was under traffic load incoming when the >>> driver loaded, CPU0 would start to poll among all the different netdev >>> queues, all on CPU0. >>> >>> The above then leads to the condition that the device is stuck polling >>> even if the affinity gets updated from user space, and the polling will >>> continue until traffic stops. >>> [...] >> As we can see in the above trace the initial affinity for the IRQ 1478 was >> correctly set as per the default_smp_affinity mask which includes CPU 42, >> however, later on, it is updated with CPU3 which is returned from >> cpumask_local_spread(). >> >>> Maybe the right thing is to fix which CPUs are passed in as the valid >>> mask, or make sure the kernel cross checks that what the driver asks >>> for is a "valid CPU"? >>> >> Sure, if we can still reproduce the problem that your patch was fixing then >> maybe we can consider adding a new API like cpumask_local_spread_irq in >> which we should consider deafult_smp_affinity mask as well before returning >> the CPU. > I'm sure I don't have a reproducer of the original problem any more, it > is lost somewhere 8 years ago. I'd like to be able to repro the original > issue, but I can't. > > Your description of the problem makes it obvious there is an issue. It > appears as if cpumask_local_spread() is the wrong function to use here. > If you have any suggestions please let me know. > > We had one other report of this problem as well (I'm not sure if it's > the same as your report) > https://lkml.org/lkml/2021/3/28/206 > https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20210125/023120.html How about we introduce a new API just for IRQ spreading, cpumask_local_spread_irq() and then utilize the default_smp_affinity mask in that before returning the CPU? Although, I think the right way to deal with this would be to fix this from the source that is where the CPU mask is assigned to an IRQ for the very first time. -- Thanks Nitesh
