Re: Very high interrupts on a supermicro machine.

2005-10-21 Thread Matt Rowley
> > Right now my box is doing ~28,000pps per direction per interface (out > > public, in public, out internal, in internal), totalling around > > 112kpps. It doesn't seem to want to go any higher than that. I've just > > tried moving the internal connection off of the dualport PCI-X card > > and on

Re: Very high interrupts on a supermicro machine.

2005-10-21 Thread Henning Brauer
* dormando <[EMAIL PROTECTED]> [2005-10-21 01:08]: > Did you make any other configuration changes? > > Right now my box is doing ~28,000pps per direction per interface (out > public, in public, out internal, in internal), totalling around > 112kpps. It doesn't seem to want to go any higher than th

Re: Very high interrupts on a supermicro machine.

2005-10-20 Thread dormando
Did you make any other configuration changes? Right now my box is doing ~28,000pps per direction per interface (out public, in public, out internal, in internal), totalling around 112kpps. It doesn't seem to want to go any higher than that. I've just tried moving the internal connection off of the

Re: Very high interrupts on a supermicro machine.

2005-10-20 Thread Michael Blodgett
[mailto:[EMAIL PROTECTED] On Behalf Of dormando Sent: Monday, October 17, 2005 8:29 PM To: misc@openbsd.org Subject: Very high interrupts on a supermicro machine. Hey all, Attached is a dmesg of one of a pair of supermicro based firewalls I recently bought. I had set them up as a CARP/pfsync r

Re: Very high interrupts on a supermicro machine.

2005-10-19 Thread dormando
t; if (!(ifq)->ifq_congestion) \ > > if_congestion(ifq); \ > > > > that means the congestion flag will never be set. > > or you add a return; as first statement in if_congestion() in if.c. > > > > > >

Re: Very high interrupts on a supermicro machine.

2005-10-19 Thread Henning Brauer
f_congestion() in if.c. > > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > On Behalf Of dormando > > Sent: Monday, October 17, 2005 8:29 PM > > To: misc@openbsd.org > > Subject: Very high interrupts on a superm

Re: Very high interrupts on a supermicro machine.

2005-10-18 Thread dormando
\ > > that means the congestion flag will never be set. > or you add a return; as first statement in if_congestion() in if.c. > > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > On Behalf Of dormando > > Sent: Monday,

Re: Very high interrupts on a supermicro machine.

2005-10-18 Thread Schöberle Dániel
Sent: Monday, October 17, 2005 8:29 PM > To: misc@openbsd.org > Subject: Very high interrupts on a supermicro machine. > > Hey all, > > Attached is a dmesg of one of a pair of supermicro based firewalls I > recently bought. I had set them up as a CARP/pfsync redundant pair of

Re: Very high interrupts on a supermicro machine.

2005-10-17 Thread dormando
On 10/17/05, dormando <[EMAIL PROTECTED]> wrote: > Hey all, [...] My apologies for mime'ing the dmesg :( I post here once a year or so. It looks like the latest snapshot from the FTP does a lot better with interrupts (about 150k pps before getting into the danger area), and interrupts never go a

Very high interrupts on a supermicro machine.

2005-10-17 Thread dormando
Hey all, Attached is a dmesg of one of a pair of supermicro based firewalls I recently bought. I had set them up as a CARP/pfsync redundant pair of frontend firewalls for our network. However, after they reached 15,000 interrupts per second (~ 110 megabits of our site traffic), they passed 90% CPU