Re: scheduler (sched_4bsd) questions
From: Julian Elischer (julian_at_elischer.org)
Date: 09/19/04
- Previous message: John-Mark Gurney: "Re: better MTU support..."
- In reply to: John Baldwin: "Re: scheduler (sched_4bsd) questions"
- Next in thread: Julian Elischer: "Re: scheduler (sched_4bsd) questions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 19 Sep 2004 00:10:07 -0700 To: John Baldwin <jhb@FreeBSD.org>
John Baldwin wrote:
> On Saturday 18 September 2004 01:42 pm, Stephan Uphoff wrote:
>
>>On Fri, 2004-09-17 at 21:20, Julian Elischer wrote:
>>
>>>Stephan Uphoff wrote:
>>>
>>>>If this is true kernel threads can be preempted while holding
>>>>for example the root vnode lock (or other important kernel
>>>>resources) while not getting a chance to run until there are no more
>>>>user processes with better priority.
>>>
>>>This is also true, though it is a slightly more complicated thing than
>>>that.
>>>Preempting threads are usually interrupt threads and are thus usually
>>>short lived,.
>>
>>But interrupt threads often wake up other threads ...
>
>
> That are lower priority and thus won't be preempted to. Instead, they run
> when the interrupt thread goes back to sleep after it finishes.
though that may still be before the original preempted thread gets run..
that reminds me..
John, we should add a flag to setrunqueue to add a preempted thread back at the
FRONT of it's runqueue.. So that it gets a chance to use the rest of its slot..
the alternative is to keep a special "stack" (per cpu) of preempted threads so
that we com back to the thread that we preempted.
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: John-Mark Gurney: "Re: better MTU support..."
- In reply to: John Baldwin: "Re: scheduler (sched_4bsd) questions"
- Next in thread: Julian Elischer: "Re: scheduler (sched_4bsd) questions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: scheduler (sched_4bsd) questions
... John Baldwin wrote: ... >>But interrupt threads often wake
up other threads ... ... > That are lower priority and thus won't be preempted to. ...
(freebsd-arch) - Re: scheduler (sched_4bsd) questions
... > John Baldwin wrote: ... >> That are lower priority and thus
won't be preempted to. ... > though that may still be before the original preempted thread
gets run.. ... The scheduler can already detect this by noting that curthread is being
passed ... (freebsd-arch)