From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Mon,  1 Mar 2010 17:50:24 -0500
To: lucio@proxima.alt.za, 9fans@9fans.net
Message-ID: <6dad9c1dad4c0a70b830a69551f06292@coraid.com>
In-Reply-To: <9d0c94c5d5934f8052d853aad2c1699c@proxima.alt.za>
References: <9d0c94c5d5934f8052d853aad2c1699c@proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Interrupt saturation
Topicbox-Message-UUID: de3399da-ead5-11e9-9d60-3106f5b1d025

> > looks like you just have HZ set to 1000.
> >  stats isn't counting on that.
> >
> How does one change that?

i wouldn't suspect that one would want to.
the higher clock rate allows more precise
scheduling.  the extra overhead should be
unnoticable on a 2.6ghz processor, except via
stats.

> > also, 113 ethernet interrupts/sec is a pretty
> > good clip.
>
> Yes, that's also a bit steep.  Intel chip, maybe I should install the
> 3Com card I had on the old hardware.  I changed from a 900MHz board to
> a newer, 2.6GHz device with some (additional) peripherals built in.
> Didn't expect a weird stats display.

i would imagine that you're getting this kind of
interrupt load from the nic because you're getting
a lot of packets.

do you suspect the interrupt load is a problem, or
are you just bothered by stats?

- erik