aboutsummaryrefslogtreecommitdiffstats
path: root/net/unix/af_unix.c
diff options
context:
space:
mode:
authorRik van Riel <[email protected]>2024-12-05 02:03:16 +0000
committerIngo Molnar <[email protected]>2024-12-06 09:26:20 +0000
commit6db2526c1d694c91c6e05e2f186c085e9460f202 (patch)
treea3c4e31b2501fe43c01645602be6d515f2b9155c /net/unix/af_unix.c
parentx86/mm/tlb: Also remove local CPU from mm_cpumask if stale (diff)
downloadkernel-6db2526c1d694c91c6e05e2f186c085e9460f202.tar.gz
kernel-6db2526c1d694c91c6e05e2f186c085e9460f202.zip
x86/mm/tlb: Only trim the mm_cpumask once a second
Setting and clearing CPU bits in the mm_cpumask is only ever done by the CPU itself, from the context switch code or the TLB flush code. Synchronization is handled by switch_mm_irqs_off() blocking interrupts. Sending TLB flush IPIs to CPUs that are in the mm_cpumask, but no longer running the program causes a regression in the will-it-scale tlbflush2 test. This test is contrived, but a large regression here might cause a small regression in some real world workload. Instead of always sending IPIs to CPUs that are in the mm_cpumask, but no longer running the program, send these IPIs only once a second. The rest of the time we can skip over CPUs where the loaded_mm is different from the target mm. Reported-by: kernel test roboto <[email protected]> Signed-off-by: Rik van Riel <[email protected]> Signed-off-by: Ingo Molnar <[email protected]> Cc: Dave Hansen <[email protected]> Cc: Andy Lutomirski <[email protected]> Cc: Mathieu Desnoyers <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: Linus Torvalds <[email protected]> Link: https://lore.kernel.org/r/20241204210316.612ee573@fangorn Closes: https://lore.kernel.org/oe-lkp/[email protected]/
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions