From owner-freebsd-current@FreeBSD.ORG  Mon Nov  3 19:32:31 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4F61316A4CF
	for <current@freebsd.org>; Mon,  3 Nov 2003 19:32:31 -0800 (PST)
Received: from smtp.mho.com (smtp.mho.net [64.58.4.6])
	by mx1.FreeBSD.org (Postfix) with SMTP id 9C7DC43F85
	for <current@freebsd.org>; Mon,  3 Nov 2003 19:32:29 -0800 (PST)
	(envelope-from scottl@freebsd.org)
Received: (qmail 71200 invoked by uid 1002); 4 Nov 2003 03:32:29 -0000
Received: from unknown (HELO ?10.4.1.5?) (64.58.1.252)
  by smtp.mho.net with SMTP; 4 Nov 2003 03:32:29 -0000
Date: Mon, 3 Nov 2003 20:35:27 -0700 (MST)
From: Scott Long <scottl@freebsd.org>
X-X-Sender: scottl@pooker.samsco.home
To: Doug White <dwhite@gumbysoft.com>
In-Reply-To: <20031103184243.B86138@carver.gumbysoft.com>
Message-ID: <20031103203242.A34233@pooker.samsco.home>
References: <20031104012530.4A8D82A8EB@canning.wemm.org>
 <20031103184243.B86138@carver.gumbysoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: HEADSUP: Committing new interrupt code, tree will be broken 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2003 03:32:31 -0000

On Mon, 3 Nov 2003, Doug White wrote:> On Mon, 3 Nov 2003, Peter Wemm wrote:
>
> > John Baldwin wrote:
> > >
> > > On 03-Nov-2003 John Baldwin wrote:
> > > > I'm committing the new i386 interrupt and SMP code, so buckle your
> > > > seat belts. :)  I'll be intentionally breaking the kernel build at
> > > > the start and re-enable it with the last commit when I am done.
> > >
> > > I've finished committing everything but am waiting for some kernel
> > > compiles on virgin trees to finish to make sure I didn't miss anything.
> > > The -current waters should be safe again though.
>
> My Dell PE1750 hangs up solid under network load.
>
> Its a serverworks of some recent variation, 2x2.4GHz xeons. BIOS A05. bge
> ethernet x2.  Apachebench will mash it dead in a few seconds.
>

Sam just discovered some locking problems in the IPv4 stack.  Can you
update to his recent commit and retry?  With the new interrupt routing
code, you can either get your interrupts or you can't.  High load
should not be affected by it.

Scott