From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8bedeb6480059bea89539741b190d3f9@proxima.alt.za>
To: 9fans@9fans.net
Date: Mon,  1 Mar 2010 19:39:36 +0200
From: lucio@proxima.alt.za
In-Reply-To: <13426df11002281913r2b94cca1h1f09d2df6d4c460f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Interrupt saturation
Topicbox-Message-UUID: de106dd4-ead5-11e9-9d60-3106f5b1d025

> workstation only? I.e. it is not running venti?

Thanks for the chance to follow up.  I implemented quanstro's
enhancement to /proc, and this is what I get right now, some
twenty-four hours after starting up:

          3           0                    0 debugpt
          7           0                    0 mathemu
          8           0                    0 doublefault
          9           0                    0 mathover
         14           0                    0 fault386
         15           0                    0 unexpected
         16           0                    0 matherror
         50          18             76160483 clock
         51          19                    0 lapicerror
         63          31                    0 lapicspurious
         65           1                15761 kbd
         73          11              9799735 ether0
         81           6                    0 floppy
         89           3               124777 ac97audio
         97           5                    0 usbuhci
        105           9                    0 usbuhci
        113          11                    0 usbuhci
        121          10                    0 usbehci
        129          15                   82 sdD (ata)
        137           7                    0 lpt
        145          12               213171 kbdaux

The stuff Erik displayed looked a lot worse, so maybe it's just that
I'm not used to having stats(1) display a solid block for the
Interrupts.  Still, I wish cpu cycles could be better utilised.

And, tes, it's effectively a diskless terminal.

++L