From: Arjan van de Ven <arjanv@redhat.com>
To: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.67-mm4 & IRQ balancing
Date: 22 Apr 2003 12:32:13 +0200 [thread overview]
Message-ID: <1051007533.1420.6.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030422120630.4048a8b1.philippe.gramoulle@mmania.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
>
> Booted with "noirqbalance" & started irqbalance:
>
> $ cat /proc/interrupts
> CPU0 CPU1
> 0: 73897 247288143 IO-APIC-edge timer
> 1: 38421 56 IO-APIC-edge i8042
> 2: 0 0 XT-PIC cascade
> 3: 177 0 IO-APIC-edge serial
> 8: 107607 0 IO-APIC-edge rtc
> 12: 3 0 IO-APIC-edge i8042, i8042, i8042, i8042
> 15: 32 118 IO-APIC-edge ide1
> 18: 12602 1159 IO-APIC-level EMU10K1
> 19: 454172 15987 IO-APIC-level uhci-hcd
> 20: 494005 0 IO-APIC-level eth0
> 22: 717483 38681 IO-APIC-level aic7xxx
> 23: 0 0 IO-APIC-level uhci-hcd
> NMI: 0 0
> LOC: 247366287 247364170
> ERR: 0
> MIS: 0
this looks reasonably in balance; your biggest irq source is the timer,
which gets a cpu all of it's own and the rest of your irq sources is
hardly noticable and all go together on the other cpu for that reason to
counterbalance the "high rate" timer.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-22 10:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 23:58 Philippe Gramoullé
2003-04-19 0:51 ` Andrew Morton
2003-04-19 13:39 ` Philippe Gramoullé
2003-04-19 20:38 ` Andrew Morton
2003-04-22 10:06 ` Philippe Gramoullé
2003-04-22 10:32 ` Arjan van de Ven [this message]
2003-04-23 19:41 ` Bill Davidsen
2003-04-23 20:13 ` Zwane Mwaikambo
2003-04-24 21:32 ` Bill Davidsen
2003-04-25 9:03 ` Arjan van de Ven
2003-04-23 20:15 ` Andrew Morton
2003-04-19 1:03 Nakajima, Jun
2003-04-19 12:21 Chuck Ebbert
2003-04-19 13:14 ` Philippe Gramoullé
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=1051007533.1420.6.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.gramoulle@mmania.com \
/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
all inboxes | Powered by JetHome®