From owner-freebsd-current@FreeBSD.ORG  Mon Nov  3 21:30:26 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 02AA316A4CE; Mon,  3 Nov 2003 21:30:26 -0800 (PST)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5E7C143FB1; Mon,  3 Nov 2003 21:30:25 -0800 (PST)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 51D2572DA3; Mon,  3 Nov 2003 21:30:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 4ECD772DA2; Mon,  3 Nov 2003 21:30:25 -0800 (PST)
Date: Mon, 3 Nov 2003 21:30:25 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: Scott Long <scottl@freebsd.org>
In-Reply-To: <20031103203242.A34233@pooker.samsco.home>
Message-ID: <20031103212841.A90051@carver.gumbysoft.com>
References: <20031104012530.4A8D82A8EB@canning.wemm.org>
	<20031103203242.A34233@pooker.samsco.home>
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 05:30:26 -0000

On Mon, 3 Nov 2003, Scott Long wrote:

> > 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.

(for the record)

Tried turning off mpsafenet, no luck.  Will try disabling ACPI tomorrow.

I'm hoping its not some silly bge bug that happens to manifest only in
-current. I ran some extensive load testing with this and another
single-proc box on 4.9 without any issues, but thats obviously not
directly comparable.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org