hrtimer: Keep track of first expiring timer per clock base

Browse source

Evaluating the next expiry time of all clock bases is cache line expensive
as the expiry time of the first expiring timer is not cached in the base
and requires to access the timer itself, which is definitely in a different
cache line.

It's way more efficient to keep track of the expiry time on enqueue and
dequeue operations as the relevant data is already in the cache at that
point.

Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://patch.msgid.link/20260224163431.404839710@kernel.org

...

This commit is contained in:

Thomas Gleixner 2026-02-24 17:38:28 +01:00 • committed by Peter Zijlstra

parent b95c4442b0

commit eddffab828

2 changed files with 36 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

include/linux/hrtimer_defs.h

View file

37

kernel/time/hrtimer.c

View file