From owner-freebsd-hackers Thu Jul 18 0:28:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 333EC37B401 for ; Thu, 18 Jul 2002 00:28:35 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 611B043E5E for ; Thu, 18 Jul 2002 00:28:34 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.3/8.12.3) with ESMTP id g6I7SX1f023474 for ; Thu, 18 Jul 2002 01:28:33 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 18 Jul 2002 01:27:01 -0600 (MDT) Message-Id: <20020718.012701.40618865.imp@bsdimp.com> To: hackers@freebsd.org Subject: Interrupt storms on current handled better than stable From: "M. Warner Losh" X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Just wanted to let folks know that I'm very happy with the way that interrupt storms are handled in current. They do eat all the CPU, which is unfortunate. However, they don't keep me from breaking into the debugger, or pinging the machine! When I call boot 0 from the debugger, the system becomes very responsive for the short period of time that I can interact with it. This is very cool. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message