lkml.org 
[lkml]   [2012]   [Mar]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] watchdog: Make sure the watchdog thread gets CPU on loaded system
From
Date
On Thu, 2012-03-15 at 11:54 -0400, Don Zickus wrote:
> > > Why did watchdog() reset the scheduling policy seven instructions
> > > before exiting? Seems pointless.
> >
> > It has been introduced by Thomas in cba9bd22. To be honest I don't
> > understand why it makes a sense?
>
> Yeah I noticed that too. I didn't bother questioning it either when
> it
> went in. I just assumed Thomas and Peter know scheduling a lot better
> than I do. :-)

I just dug through my IRC logs and the reason is that running the entire
exit path as a highest priority RT task incurs a latency spike to other
tasks running on the system (313us). Since there's absolutely no point
in running the exit path as a RT task, tglx made it not do that.


\
 
 \ /
  Last update: 2012-03-15 17:07    [W:0.069 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site