Summary: | rtprio(1): (id|rt)prio priority resets when new thread is created | ||
---|---|---|---|
Product: | Base System | Reporter: | c.kworr |
Component: | threads | Assignee: | freebsd-threads (Nobody) <threads> |
Status: | Open --- | ||
Severity: | Affects Only Me | ||
Priority: | Normal | ||
Version: | Unspecified | ||
Hardware: | Any | ||
OS: | Any |
Description
c.kworr
2009-12-17 19:20:03 UTC
Responsible Changed From-To: freebsd-bugs->freebsd-threads Over to maintainer(s). idle priority is not supported by libthr yet, the reason I don't want to enable it is kernel also may have trouble to handle idle thread. a thread in kernel holds a non-mutex lock and is preempted, it is possible to be starved by other threads, such a priority reversal can make system work rather badly. I think the thread preemption may should work in opposite direction. default, it should always be disabled in kernel, only some code knows where it is OK to be preempted: 1. interrupt thread preempt others 2. a thread returned to userland 3. some kernel code, it knows it is doing large computation, or non-sense code, it turns on preemption, when it exits such code, it turns off preemption. idle thread does not mean it is not execute important code, idle thread can execute any code in kernel, so idle does not mean it is insignificant, the word 'idle' is bogus, priority does not mean it is important or less important. For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped |