From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Interrupt saturation
Date: Tue, 2 Mar 2010 06:01:53 +0200 [thread overview]
Message-ID: <3cae5bad69c37f83b8df23a11a3829d2@proxima.alt.za> (raw)
In-Reply-To: <6dad9c1dad4c0a70b830a69551f06292@coraid.com>
> do you suspect the interrupt load is a problem, or
> are you just bothered by stats?
The latter, I replaced the workstation hardware bacause of a power
supply fan failure and the most noticeable difference was stats'
behaviour.
In passing, has anyone looked at fixing the uneven width of the last
column in a multi-host stats display? I tried, but it seemed such a
convoluted computation I couldn't figure out how the last column's
width turned out a good few pixels wider than the others. This is
particularly visible with many narrow columns (I have had up to eight
of them).
++L
prev parent reply other threads:[~2010-03-02 4:01 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
2010-03-02 4:01 ` lucio [this message]
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=3cae5bad69c37f83b8df23a11a3829d2@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).