Peter Dufault wrote: > > I've got a synch_yield() in kern_synch and a call into it from yield() > > in kern_thread that duplicates the yield() behavior for the non-RTPRIO, > > non-sched_yield() condition. synch_yield() also KASSERTS > > that p == curproc since nothing else makes sense. > > While we're discussing yield here's a question. > > The difference between yield() and sched_yield() is that yield unconditionally > yields while sched_yield() won't if you are the highest priority process > and the only process in your run queue. Does anyone know the > reuirements on yield() and would it continue to function for us if > it worked the same as sched_yield()?
FWIW, the yield syscall is _not_ built into libc, so I doubt there will be anything that actually uses it. I think you should just keep sched_yield(). -- John Birrell - j...@cimlogic.com.au; j...@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
