On Wednesday 10 May 2006 12:49, Lee Revell wrote:
> On Wed, 2006-05-10 at 08:25 +0200, Thomas Gleixner wrote:
> > On Wed, 2006-05-10 at 02:15 -0400, Steven Rostedt wrote:
> > > I've CC'd Thomas Gleixner. I beleive that the hrtimers code now uses
> > > priorities. That is, when a timer is to go off, the hrtimer softirq
> > > inherits the priority of the task that created the timer. Thomas,
> > > correct me if I'm wrong. But I also believe this code is a work in
> > > progress, and the more feedback of what people want/need the better we
> > > can make the code do just that.
> > >
> > > Is the high res timers turned on?
> >
> >
http://www.linutronix.de/index.php?module=News&id=cntnt01&cntnt01action=detail&cntnt01articleid=8&cntnt01dateformat=%b%20%d,
%20%Y&cntnt01returnid=31
> >
> > This is only true, when high resolution timers are enabled.
>
> Is there any solution for the !CONFIG_HIGH_RES_TIMERS case? I for one
> can't use it because my hardware doesn't support it (no local APIC).
Thanks for forwarding the link, Lee. That's helpful information.
Thomas, does this dynamic priority support work when running softirq-timer/0
at SCHED_OTHER? I tried, and it seems to work here, I just want to make sure
it's valid to do so.
Wolfgang
Received on Wed May 10 16:15:07 2006
This archive was generated by hypermail 2.1.8 : Wed May 10 2006 - 16:15:07 EEST