RFC RFC: using hrtimers for in-kernel timeouts
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | introduce schedule_timeout_hrinclude/ kernel/ | +50 | 0 replies | |
| 2/3 | use hrtimer in select and pselectfs/ include/ | +24 | 0 replies | |
| 3/3 | change schedule_timeout to use hrtimerskernel/ kernel/ | +90 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/3] RFC: using hrtimers for in-kernel timeouts
I've played around with the new timer statistics to see which timers might benefit of being moved from traditional timers to hrtimers.
Since my understanding is that timer_list timers are not really meant to expire, this seems to include a lot of what comes in through schedule_timeout, in particular select() and futex wait.
I have no idea if what I was attempting is even the right approach to start with, but I want to share the patches in case it is ;-).
Maybe someone is interested in running some low-level benchmarks on this or point out any bugs in the code.
Arnd <><
--