On 19-Oct-01 Alex Levine wrote:
> John Baldwin wrote:
>
>>On 18-Oct-01 Alexander Langer wrote:
>>
>>>Thus spake Alex Levine ([EMAIL PROTECTED]):
>>>
resetpriority() calls maybe_resched() at the end after updating p_usrpri
based on changed p_estcpu.
maybe_resched() uses curpriority_c
John Baldwin wrote:
>On 18-Oct-01 Alexander Langer wrote:
>
>>Thus spake Alex Levine ([EMAIL PROTECTED]):
>>
>>>resetpriority() calls maybe_resched() at the end after updating p_usrpri
>>>based on changed p_estcpu.
>>>maybe_resched() uses curpriority_cmp to compare priorities of current
>>>and
On 18-Oct-01 Alexander Langer wrote:
> Thus spake Alex Levine ([EMAIL PROTECTED]):
>
>> resetpriority() calls maybe_resched() at the end after updating p_usrpri
>> based on changed p_estcpu.
>> maybe_resched() uses curpriority_cmp to compare priorities of current
>> and given process and this
Thus spake Alex Levine ([EMAIL PROTECTED]):
> resetpriority() calls maybe_resched() at the end after updating p_usrpri
> based on changed p_estcpu.
> maybe_resched() uses curpriority_cmp to compare priorities of current
> and given process and this function ( curpriority_cmp ) uses p_priority
FreeBSD 4-stable. Suspect the same in FreeBSD-current.
resetpriority() calls maybe_resched() at the end after updating p_usrpri
based on changed p_estcpu.
maybe_resched() uses curpriority_cmp to compare priorities of current
and given process and this function ( curpriority_cmp ) uses p_priorit
5 matches
Mail list logo