Re: [patch 00/43] ktimer reworked

Ingo Molnar <mingo@xxxxxxx> wrote:
>
> we could merge the two by driving 'timeouts' via ktimers too - but there
> would be some unavoidable overhead to things like the TCP stack. But
> ktimers cannot be merged into timeouts, that's sure.

I think you guys have an advantage over me because you've been discussing
and thinking about this terminology for months. IOW, your lips are moving
but all I hear is blah, blah, blah ;)

For instance, when Kyle came out with his one-sentence description of
timers versus timeouts, I thought he had them backwards. Only apparently
he didn't.

So either it's all confusing, or I'm dumb, or both. I can evade
investigation of that by claiming that we should seek something which is
unconfusing to even dumb people.

We have timer_lists. But you say they don't suit precision timers. Fine.
So why cannot we call the new precision timers something like "precision
timers" and avoid this semantic confusion over timeouts versus timers?

IOW: leave timer_lists alone. Just add the needed new subsystem and use it.

I guess old-timers can mentally do s/ktimeout/timer_list/ whenever they
come across the danged thing, but it's a bit painful. If we called them
"timer_list" and "hrtimer", things would be much clearer. Plus that's a
description of what they *are*, rather than of how we expect them to be
applied.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [PATCH] ktimers subsystem 2.6.14-rc2-kt5
    ... I asked, had no confusion with what they meant. ... timeouts are for situations that are for things that lasted too ... and timers were the other way around and should always be ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: 2.6.13-rt6, ktimer subsystem
    ... > the kernel: timeouts and timers. ... The hashed tree I used in HRT instead of the cascade, ... > with an increasing number of timers, due to the cascading design. ...
    (Linux-Kernel)
  • Re: (BUG?) round_jiffies() is non-monotonic on SMP
    ... Alan Stern wrote: ... where you don't really care when exactly timers will fire... ... I don't think timeouts EVER have that guarantee between different cpus; ... no objection per se, but I would almost argue we should convert such ...
    (Linux-Kernel)
  • Re: Process uses high CPU usage but no performance drop ??
    ... did not have access to any sophisticated routines at that time ... The comment on timers makes me a bit nervous as we do use quite a few ... 'efficient' way to check these timeouts without slogging the CPU load? ... Sleep is rarely needed and is often misused. ...
    (microsoft.public.vc.mfc)
  • Re: [patch 00/43] ktimer reworked
    ... HRES timers to the -rt tree is to integrate them into the existing timer ... ways to merge high-res timers into the timer wheel. ... The two usage scenarios (timeouts and ...
    (Linux-Kernel)