* Roman Zippel <[email protected]> wrote:
> > > > e.g. we dont want a watchdog from being
> > > > overload-able via too many timeouts in the timer wheel ...
> > >
> > > Please explain.
> >
> > e.g. on busy networked servers (i.e. ones that do have a need for
> > watchdogs) the timer wheel often includes large numbers of timeouts,
> > 99.9% of which never expire. If they do expire en masse for whatever
> > reason, then we can get into overload mode: a million timers might have
> > to expire before we get to process the watchdog event and act upon it.
> > This can delay the watchdog event significantly, which delay might (or
> > might not) matter to the watchdog application.
>
> I already mentioned earlier that it's possible to reduce the timer
> load by using a watchdog timer to filter most of these events, so that
> you get into the interesting situation that most kernel timer actually
> do expire and suddenly you easily can have more "timers" than
> "timeouts".
this sentence does not parse at all, for me. Here's the effort i did
trying to decypher it:
Firstly, you mention 'watchdog' without clarifying whether it's the
examplary watchdog we were talking about above, or whether it's some
other, new mechanism. The former makes no sense (what does the watchdog
timer in a random driver have to do with the millions of network timers
i was talking about, and how could it be used to filter anything?), the
later you dont explain.
Secondly, the above sentence is the first time in the ktimer discussion
that you ever mentioned the word 'filter', and you never mentioned the
word 'watchdog' outside of the example we were discussing, so i'm
curious about the source of the above "I already mentioned earlier"
statement. When earlier? Which email? Frankly, the whole paragraph reads
as if from another planet, i see the words but the content seems totally
out of context and makes no sense to me.
So i cannot even agree or disagree with anything you said in that
sentence, because the sentence simply does not parse. Please enlighten
me!
Ingo
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
