RFC timerfd -- implement missing parts to checkpoint and restore timerfd state
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | timerfd: Implement show_fdinfo methodfs/ | +9 | 2 replies | |
| 2/2 | docs: procfs -- Document timerfd outputDocumentation/ | +9 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [rfc 0/2] timerfd -- implement missing parts to checkpoint and restore timerfd state
Timerfd interface provides to user-space almost all data needed to checkpoint and restore it, the only missing parts are @clockid (and while @ticks can be read by simple read() call there is no way to write its value back). The series exports them to userspace via /proc/pid/fdinfo/N interface and with write() call one can setup @ticks back to a timer.
Please take a look. This is rfc to figure out if there a better way to handle timerfds (maybe ioctls with complete timer context or somthing). Also I'm not sure in one aspect -- if someone sets non-zero @ticks to a timer, should I mark it as expired? Thomas, could you please give me some advice on it?
Cyrill