diff options
| author | Yujun Dong <[email protected]> | 2024-12-30 14:16:24 +0000 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2025-03-20 09:03:52 +0000 |
| commit | 3785c7dbae0f733f13f8857beaaada5d7dc63e02 (patch) | |
| tree | 85b00782c78e666eacf602e51ac3833860a75b14 /samples/rust/rust_driver_platform.rs | |
| parent | sched/debug: Remove CONFIG_SCHED_DEBUG (diff) | |
| download | kernel-3785c7dbae0f733f13f8857beaaada5d7dc63e02.tar.gz kernel-3785c7dbae0f733f13f8857beaaada5d7dc63e02.zip | |
cpuidle, sched: Use smp_mb__after_atomic() in current_clr_polling()
In architectures that use the polling bit, current_clr_polling() employs
smp_mb() to ensure that the clearing of the polling bit is visible to
other cores before checking TIF_NEED_RESCHED.
However, smp_mb() can be costly. Given that clear_bit() is an atomic
operation, replacing smp_mb() with smp_mb__after_atomic() is appropriate.
Many architectures implement smp_mb__after_atomic() as a lighter-weight
barrier compared to smp_mb(), leading to performance improvements.
For instance, on x86, smp_mb__after_atomic() is a no-op. This change
eliminates a smp_mb() instruction in the cpuidle wake-up path, saving
several CPU cycles and thereby reducing wake-up latency.
Architectures that do not use the polling bit will retain the original
smp_mb() behavior to ensure that existing dependencies remain unaffected.
Signed-off-by: Yujun Dong <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'samples/rust/rust_driver_platform.rs')
0 files changed, 0 insertions, 0 deletions
