From: george anzinger <george@mvista.com>
To: Richard Zidlicky <Richard.Zidlicky@stud.informatik.uni-erlangen.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Replace timer_bh with tasklet
Date: Tue, 18 Jun 2002 16:17:45 -0700 [thread overview]
Message-ID: <3D0FBF99.C0A8AD5B@mvista.com> (raw)
In-Reply-To: 20020619004652.D2079@linux-m68k.org
Richard Zidlicky wrote:
>
> On Tue, Jun 18, 2002 at 11:07:32AM -0700, george anzinger wrote:
>
> >
> > I reasoned that the timers, unlike most other I/O, directly drive the system.
> > For example, the time slice is counted down by the timer BH. By pushing the
> > timer out to ksoftirqd, running at nice 19, you open the door to a compute
> > bound task running over its time slice (admittedly this should be caught on
> > the next interrupt).
>
> I have had some problems with timers delayed up to 0.06s in 2.4 kernels,
> could that be this problem?
>
It could be. Depends on what was going on at the time. In most cases, however,
the next interrupt should cause a call to softirq and thus run the timer list. This
would seem to indicate at 20ms delay at most (first call busys softirq thru a 10ms tick
followed by recovery at the next tick).
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2002-06-18 23:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 3:45 [PATCH] Replace timer_bh with tasklet george anzinger
2002-06-18 4:06 ` Linus Torvalds
2002-06-18 18:07 ` george anzinger
2002-06-18 22:46 ` Richard Zidlicky
2002-06-18 23:17 ` george anzinger [this message]
2002-06-19 11:43 ` Richard Zidlicky
2002-06-18 4:15 ` David S. Miller
2002-06-18 17:01 ` george anzinger
2002-06-18 17:12 ` Matthew Wilcox
2002-06-18 18:14 ` george anzinger
2002-06-18 5:16 ` kuznet
2002-06-18 18:19 ` george anzinger
2002-06-18 18:29 ` kuznet
2002-06-20 0:39 ` george anzinger
2002-06-20 1:34 ` David S. Miller
2002-06-20 1:53 ` Robert Love
2002-06-20 1:55 ` David S. Miller
2002-06-20 2:05 ` Robert Love
2002-06-20 2:01 ` David S. Miller
2002-06-20 2:15 ` Robert Love
2002-06-20 2:23 ` David S. Miller
2002-06-20 23:54 ` george anzinger
2002-06-21 1:03 ` David S. Miller
2002-06-21 14:04 ` george anzinger
2002-06-21 14:08 ` David S. Miller
2002-06-20 8:11 ` Russell King
2002-06-20 8:09 ` David S. Miller
2002-06-20 8:16 ` Russell King
2002-06-20 8:13 ` Russell King
2002-06-20 14:33 ` kuznet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D0FBF99.C0A8AD5B@mvista.com \
--to=george@mvista.com \
--cc=Richard.Zidlicky@stud.informatik.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.