From owner-freebsd-current Tue Apr 17 16: 4:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CBEB837B440 for ; Tue, 17 Apr 2001 16:04:31 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3HN4JL28591; Tue, 17 Apr 2001 16:04:19 -0700 (PDT) Date: Tue, 17 Apr 2001 16:04:18 -0700 From: Alfred Perlstein To: "E.B. Dreger" Cc: "'current@freebsd.org'" , Matt Dillon , "Justin T. Gibbs" , Doug Barton Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417160418.X976@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eddy+public+spam@noc.everquick.net on Tue, Apr 17, 2001 at 10:51:06PM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * E.B. Dreger [010417 15:51] wrote: > > Date: Tue, 17 Apr 2001 22:18:34 +0000 (GMT) > > From: E.B. Dreger > > > > My instinct (whatever it's worth; remember my disclaimer) is that co-op > > switching using something like tsleep() and wakeup_one() or similar would > > be more efficient than trying to screw with mutexes. > > Oops. I meant asleep(). I don't really like asleep(). asleep()/await() seem to require the schedlock to be aquired and released twice EVERY TIME they are called rather a mutex which only needs to enter the scheduler when it fails to aquire. seriously, it would be _trivial_ to: 1) make interrupts the only thing that could switch, or 2) turn interrupt related locks into spinlocks that do the equivelant of splhigh on that cpu. any further discussion of the underlying implementation is a waste of time and I refuse to do it any further. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] http://www.egr.unlv.edu/~slumos/on-netbsd.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message