From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <2f9f914d7711bc393368ab53809b1c97@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat, 29 Aug 2009 13:25:46 -0400
To: 9fans@9fans.net
In-Reply-To: <3e1162e60908291020t21a67c2m4ac3504868cb95b6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] new 9atom.iso
Topicbox-Message-UUID: 5be63960-ead5-11e9-9d60-3106f5b1d025

> Now that I've had a chance to really examine the system, I'm noticing a
> rather high interrupt count (1584), and I'm not exactly sure how to figure
> out what's triggering them.

i set HZ=1000.  so that accounts for 1000 of them.  i've also modified
/dev/irqalloc to count up the interrupts, so you should get a rough idea
of which irqs are responsible.  i say rough because chaned interrupts
can confuse the matter a bit.

> I did not install venti.  I just configured my ip address for DHCP, and I've
> got aux/timesync running (I think that was suspect before for some reason).
>  Stats shows interrupts as a solid rectangle of activity all the time.

i get that too from stats.  it's just tuned to HZ=100.  the reason for the
increase is so that millisecond sleeps can work a bit better.  on all the
systems i use, the overhead is not worth worring about.

- erik