Re: thread_sanity_check()

2002-07-12 Thread John Baldwin


On 11-Jul-2002 Julian Elischer wrote:
 all gone now..

Ok, I didn't mind it being there, just maybe under INVARIANTS instead
is all.

 On Thu, 11 Jul 2002, John Baldwin wrote:
 
 Considering the incredible amount of complaining over having a
 cred_free_thread() function conditionally compiled into the kernel
 that only did a mutex lock, decrement, and mutex unlock in the common
 case, why isn't thread_sanity_check() (or it's body) conditionally
 compiled?  It's a lot more expensive than cred_free_thread() and isn't
 even under INVARIANTS.  Pardon me if I find this a bit hypocritical.
 
 -- 
 
 John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
 Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/
 
 

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: thread_sanity_check()

2002-07-11 Thread Julian Elischer

all gone now..


On Thu, 11 Jul 2002, John Baldwin wrote:

 Considering the incredible amount of complaining over having a
 cred_free_thread() function conditionally compiled into the kernel
 that only did a mutex lock, decrement, and mutex unlock in the common
 case, why isn't thread_sanity_check() (or it's body) conditionally
 compiled?  It's a lot more expensive than cred_free_thread() and isn't
 even under INVARIANTS.  Pardon me if I find this a bit hypocritical.
 
 -- 
 
 John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
 Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message