From owner-freebsd-smp Mon Nov 27 16:38:24 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 8433837B479 for ; Mon, 27 Nov 2000 16:38:20 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id LAA00562; Tue, 28 Nov 2000 11:18:51 +1100 Date: Tue, 28 Nov 2000 11:19:24 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jonathan Lemon Cc: jburkhol@home.com, smp@FreeBSD.ORG Subject: Re: BSD/OS interrupt code In-Reply-To: <200011270238.eAR2c4R55543@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 26 Nov 2000, Jonathan Lemon wrote: > In article you write: > >I also think that BSD/OS went a little too far with this, and > >have produced code that is very difficult to understand, let > >alone maintain. I think its cool what they did, I'm humbled > >and amazed that they made it work, but I don't know that its > >right for FreeBSD. > > Seconded. This pretty much sums up my feeling too. Me too. I thought of implementing this for plain 386's 8 years ago, but didn't think it would be worth doing for 486's. Even our interrupt macros probably aren't worth doing starting with 386's (they may have negative benefits by generating large code which busts the cache). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message