 - Run sched_userret() after thread_userret().  Before, sched_userret() would    lower the priority of the returning thread to a user priority before    calling into thread_userret() which would call wakeup() which in turn would    cause the returning thread to eventually context switch rather than    completing its slice.  Allowing this thread to complete its slice first    yields a 15% performance improvement in super-smack on my dual opteron with    4BSD.
 - Run sched_userret() after thread_userret().  Before, sched_userret() would
   lower the priority of the returning thread to a user priority before
   calling into thread_userret() which would call wakeup() which in turn would
   cause the returning thread to eventually context switch rather than
   completing its slice.  Allowing this thread to complete its slice first
   yields a 15% performance improvement in super-smack on my dual opteron with
   4BSD.

jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase