On Wed, 10 Jul 2002, Bruce Evans wrote: > Hopefully there won't be any unconditional code. Unconditional code > in userret() pessimizes all syscalls. Unconditional code added by KSEIII > pessimized basic syscall overhead by 10% according to lmbench2. Mostly it's conditional.. if (p->p_flag & P_KSES) in syscall() and if (p->p_flag & P_KSES) { in userret() it's probably PROC_LOCK(p); thread_suspend_check(0); /* Can suspend or kill */ PROC_UNLOCK(p); try replace it with: if (P_SHOULDSTOP(p) { PROC_LOCK(p); thread_suspend_check(0); /* Can suspend or kill */ PROC_UNLOCK(p); } > > Bruce > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- userret() , ast() and the end of syscalls Julian Elischer
- Re: userret() , ast() and the end of syscalls David Xu
- Re: userret() , ast() and the end of syscalls John Baldwin
- RE: userret() , ast() and the end of syscalls John Baldwin
- RE: userret() , ast() and the end of syscalls John Baldwin
- RE: userret() , ast() and the end of syscalls Bruce Evans
- RE: userret() , ast() and the end of sysc... Julian Elischer
- RE: userret() , ast() and the end of... Bruce Evans
- RE: userret() , ast() and the en... Julian Elischer
- RE: userret() , ast() and the en... Julian Elischer
- RE: userret() , ast() and th... John Baldwin
- RE: userret() , ast() and th... Bruce Evans
- Re: userret() , ast() and the end of syscalls David Xu