:> problems. If WANT_RESCHED defaults to 0 by being undefined, then
:> the reschedule flag is never cleared when a context switch is made
:> and this could certainly lead to problems.
:
:Changing it to AST_RESCHED did not fix the problem for me.
:
:-Chris
Ok. I'm seeing the same behavior here too over an ssh link. I'm pretty
sure I broke need_resched and the processes are incorrectly getting too
much cpu in the face of a wakeup. I just have to find out where.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
- UP kernel performance and Matt Dillon's patches Gary Jennejohn
- Re: UP kernel performance and Matt Dillon's patc... Alfred Perlstein
- Re: UP kernel performance and Matt Dillon's ... Gary Jennejohn
- Re: UP kernel performance and Matt Dillo... Kenneth Wayne Culver
- Re: UP kernel performance and Matt Dillon's patc... Matthew Dillon
- Very weird assembly failure (was Re: UP kern... Matthew Dillon
- Re: Very weird assembly failure (was Re:... Chris Piazza
- Re: Very weird assembly failure (was... Matthew Dillon
- Re: Very weird assembly failure (was Re:... Bruce Evans
- Re: Very weird assembly failure (was... Matthew Dillon
- Re: Very weird assembly failure... Bruce Evans
- Re: UP kernel performance and Matt Dillon's ... Geoff Rehmet
- Re: UP kernel performance and Matt Dillo... Kenneth Wayne Culver
- Re: UP kernel performance and Matt D... Matthew Dillon
- Re: UP kernel performance and M... Alain Thivillon
- Re: UP kernel performance a... Matthew Dillon
- Re: UP kernel performance and Matt Dillon's patc... Chris Piazza
