9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: lucio@proxima.alt.za, 9fans@9fans.net
Subject: Re: [9fans] Interrupt saturation
Date: Mon,  1 Mar 2010 17:50:24 -0500	[thread overview]
Message-ID: <6dad9c1dad4c0a70b830a69551f06292@coraid.com> (raw)
In-Reply-To: <9d0c94c5d5934f8052d853aad2c1699c@proxima.alt.za>

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



  reply	other threads:[~2010-03-01 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28  9:55 lucio
2010-02-28 14:50 ` erik quanstrom
2010-03-01  3:13 ` ron minnich
2010-03-01 17:39   ` lucio
2010-03-01 18:00     ` erik quanstrom
2010-03-01 19:12       ` lucio
2010-03-01 22:50         ` erik quanstrom [this message]
2010-03-02  4:01           ` lucio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6dad9c1dad4c0a70b830a69551f06292@coraid.com \
    --to=quanstro@labs.coraid.com \
    --cc=9fans@9fans.net \
    --cc=lucio@proxima.alt.za \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).