From owner-freebsd-current Tue Aug 19 22:49:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA01117 for current-outgoing; Tue, 19 Aug 1997 22:49:28 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA01110; Tue, 19 Aug 1997 22:49:19 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id XAA18105; Tue, 19 Aug 1997 23:49:18 -0600 (MDT) Message-Id: <199708200549.XAA18105@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: smp@freebsd.org cc: current@freebsd.org Subject: HEADS UP: new FAST_INTR() code. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Aug 1997 23:49:18 -0600 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I just committed a bunch o' code that does several new things. - re-organization in preparation for making spl/cpl MP-safe. - 2 new variations in FAST_INTR() ISRs: - skip the check of ipending and cpl, I can't see a good reason for it and its absense makes life simpler in SMP. This might go back in if it doesn't work out... - the "giant lock" is no longer used, FAST_INTR routines can enter the kernel while other ISRs or traps are active. A simplelock is used to serialize FAST_INTR()s, but that may also go away someday. Let me know how sio code "feels", any improvements? or is it worse? silo overflows? If you get a system freeze, try to get to ddb via CNTL-PRINTSCREEN and get me a trace. I ran the system for 2-3 hours with a continuous 115200 stream in/out COM1 while rebuilding a kernel in another xterm with '-j12' and top in a 3rd xterm, all xterms on a remote machine. Ie. a good mix of sio/scsi/net INTs and syscalls. No signs of any problems. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD