diff options
| author | Thomas Gleixner <tglx@linutronix.de> | 2020-11-17 14:19:45 +0100 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2020-11-19 10:48:29 +0100 |
| commit | 372acbbaa80940189593f9d69c7c069955f24f7a (patch) | |
| tree | adb76ce0c98532922866523ded191a3a662195f8 /security/min_addr.c | |
| parent | c398960cd82b233886fbff163986f998b5a5c008 (diff) | |
tick/sched: Use tick_next_period for lockless quick check
No point in doing calculations.
tick_next_period = last_jiffies_update + tick_period
Just check whether now is before tick_next_period to figure out whether
jiffies need an update.
Add a comment why the intentional data race in the quick check is safe or
not so safe in a 32bit corner case and why we don't worry about it.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20201117132006.337366695@linutronix.de
Diffstat (limited to 'security/min_addr.c')
0 files changed, 0 insertions, 0 deletions