From owner-freebsd-arch Wed May 17 13:56:27 2000 Delivered-To: freebsd-arch@freebsd.org Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1]) by hub.freebsd.org (Postfix) with ESMTP id C1ED437B512 for ; Wed, 17 May 2000 13:56:24 -0700 (PDT) (envelope-from cp@berserker.bsdi.com) Received: from berserker.bsdi.com (cp@LOCALHOST [127.0.0.1]) by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA25889; Wed, 17 May 2000 14:56:16 -0600 (MDT) Message-Id: <200005172056.OAA25889@berserker.bsdi.com> To: Doug Rabson Cc: arch@freebsd.org Subject: Re: Sparc & api for asynchronous task execution (2) From: Chuck Paterson Date: Wed, 17 May 2000 14:56:16 -0600 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG } }I didn't realize that every function call involved a fault on the sparc }architecture - that sounds pretty nasty. Actually every function call doesn't cause a fault, every time you overflow/underflow the current set of register windows causes a fault. (Perhaps what you meant). This means that calling a function from the bottom most function will cause two faults, one for going down and one eventually as you go up. This makes going up and down when you don't overflow very fast at the expense of when you add to the total depth. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message