From: Len Brown <lenb@kernel.org>
To: Norberto Bensa <nbensa@gmx.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: core2 duo, interrupts: is this normal?
Date: Fri, 16 Mar 2007 01:31:46 -0400 [thread overview]
Message-ID: <200703160131.46789.lenb@kernel.org> (raw)
In-Reply-To: <200703152224.54607.nbensa@gmx.net>
On Thursday 15 March 2007 21:24, Norberto Bensa wrote:
> Hello,
>
> is this output, normal? I meant, why counters on CPU1 is zero? Isn't this
> balanced?
yes, it is normal.
If you had an interrupt-limited workload then irqbalance
would pick things up and spread them out.
-Len
> $ cat /proc/interrupts
> CPU0 CPU1
> 0: 4180170 0 IO-APIC-edge timer
> 1: 8060 0 IO-APIC-edge i8042
> 7: 0 0 IO-APIC-edge parport0
> 9: 0 0 IO-APIC-fasteoi acpi
> 12: 5 0 IO-APIC-edge i8042
> 16: 322297 0 IO-APIC-fasteoi uhci_hcd:usb3, libata, nvidia,
> EMU10K1
> 17: 896399 0 IO-APIC-fasteoi bttv0, eth0, libata
> 18: 72867 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb7
> 19: 27770 0 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb5
> 20: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
> 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb6
> 22: 3 0 IO-APIC-fasteoi ohci1394
> 23: 155 0 IO-APIC-fasteoi HDA Intel
> 219: 103056 0 PCI-MSI-edge libata
> NMI: 0 0
> LOC: 4077613 4077622
> ERR: 0
> MIS: 0
>
>
> Many thanks in advance,
> Norberto
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2007-03-16 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 1:24 core2 duo, interrupts: is this normal? Norberto Bensa
2007-03-16 5:31 ` Len Brown [this message]
2007-03-16 20:28 ` Arjan van de Ven
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=200703160131.46789.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbensa@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.