HEADSUP: Committing new interrupt code, tree will be broken
scottl at freebsd.org
Mon Nov 3 19:32:31 PST 2003
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.
More information about the freebsd-current