</>EmbeddedInterview

What are kernel timers, hrtimers and delays?

MediumLinux Kernel & Device Drivers

Short answer: Timers (timer_list, mod_timer) run a callback in softirq context after a delay measured in jiffies (resolution 1/HZ, e.g. 4 ms with HZ=250), suitable for timeouts that do not need precision. High-resolution timers (hrtimer) have nanosecond-based expiry using the hardware clock event device, for precise timing. For delays, use udelay/ndelay (busy-wait, for microseconds, allowed in atomic context), usleep_range (sleep, 10 µs–20 ms), and msleep/fsleep (sleep, longer).

Timer example (watchdog-style timeout)

static void mydev_timeout(struct timer_list *t)
{
    struct mydev *d = from_timer(d, t, timer);      /* timer_container_of() on newest kernels */
    dev_warn(d->dev, "no response, resetting\n");
    schedule_work(&d->reset_work);                  /* softirq context: defer anything that sleeps */
}

timer_setup(&d->timer, mydev_timeout, 0);           /* in probe */
mod_timer(&d->timer, jiffies + msecs_to_jiffies(500));   /* (re)arm */
timer_delete_sync(&d->timer);                       /* in remove (del_timer_sync on older kernels) */

hrtimer example (periodic 1 ms)

static enum hrtimer_restart tick(struct hrtimer *t)
{
    struct mydev *d = container_of(t, struct mydev, hrt);
    sample(d);
    hrtimer_forward_now(t, ms_to_ktime(1));
    return HRTIMER_RESTART;
}
hrtimer_setup(&d->hrt, tick, CLOCK_MONOTONIC, HRTIMER_MODE_REL);  /* hrtimer_init on older kernels */
hrtimer_start(&d->hrt, ms_to_ktime(1), HRTIMER_MODE_REL);

Choosing a delay

Duration Context Use
< 10 µs any udelay, ndelay
10 µs – 20 ms process usleep_range(min, max) (gives the scheduler slack to batch wake-ups)
> 10 ms process msleep, msleep_interruptible
unsure process fsleep(us) picks the right function

Pitfalls: msleep(1) can sleep much longer (rounded up to jiffies, at least 1–2 jiffies); compare jiffies with time_after() (handles wrap-around); always cancel timers synchronously before freeing their data.