From owner-freebsd-hackers Tue Aug 7 0:38:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 88E0137B405 for ; Tue, 7 Aug 2001 00:38:19 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f777dmi08218; Tue, 7 Aug 2001 00:39:49 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108070739.f777dmi08218@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: tlambert2@mindspring.com Cc: Matt Dillon , Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: Allocate a page at interrupt time In-reply-to: Your message of "Mon, 06 Aug 2001 23:27:56 PDT." <3B6F8A6C.B95966B7@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Aug 2001 00:39:48 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > It also has the unfortunate property of locking us into virtual > wire mode, when in fact Microsoft demonstrated that wiring down > interrupts to particular CPUs was good practice, in terms of > assuring best performance. Specifically, running in virtual > wire mode means that all your CPUs get hit with the interrupt, > whereas running with the interrupt bound to a particular CPU > reduces the overall overhead. Even what we have today, with > the big giant lock and redirecting interrupts to "the CPU in > the kernel" is better than that... Terry, this is *total* garbage. Just so you know, ok? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message