Re: [PATCH] i386 No-Idle-Hz aka Dynamic-Ticks 3

> I convinced my self that the next_timer... code in timer.c misses timers
> (i.e. gives the wrong answer).  I did this (after wondering due to
> performance) by scanning the whole timer list after I had the
> next_timer... answer and finding a better answer, not always, but some
> times.  That code does not address the cascade list correctly.

The timertop kernel patch accounts for all the scheduled timers. Try
to take a look at its output at /proc/top_info. Maybe it can help to
detect it.


Daniel Petrini
-- 
10LE - Linux
INdT - Manaus - Brazil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] i386 No-Idle-Hz aka Dynamic-Ticks 3
    • From: Con Kolivas <[email protected]>
  • Re: [PATCH] i386 No-Idle-Hz aka Dynamic-Ticks 3
    • From: Srivatsa Vaddagiri <[email protected]>
  • Re: [PATCH] i386 No-Idle-Hz aka Dynamic-Ticks 3
    • From: Tony Lindgren <[email protected]>
  • Re: [PATCH] i386 No-Idle-Hz aka Dynamic-Ticks 3
    • From: George Anzinger <[email protected]>

• Prev by Date: Re: my kernel sometimes did a crash, but no panic
• Next by Date: Re: my kernel sometimes did a crash, but no panic
• Previous by thread: Re: [PATCH] i386 No-Idle-Hz aka Dynamic-Ticks 3
• Next by thread: Re: [PATCH] i386 No-Idle-Hz aka Dynamic-Ticks 3
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]