From: Philippe Amelant <pamelant@linux-at-business.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: how to balance interrupts between 2 CPUs?
Date: 10 Apr 2002 14:54:54 +0200 [thread overview]
Message-ID: <1018443294.6396.10.camel@avior> (raw)
In-Reply-To: <b5926afe75.afe75b5926@water.pku.edu.cn>
Le mer 10/04/2002 à 14:23, zxj@water.pku.edu.cn a écrit :
> Hello
>
> I am using two Intel Giga NICs in a DELL PowerEdge 4600
> with 2 Intel XEON 1.8GHz CPUs.
> The matherboard is ServerWorks GC-HE.
> The OS is RedHat 7.2, and the release of kernel is "2.4.7-10smp".
>
> The CPU0 has very heavy interrupt traffic,
> you can see the following information:
Are you using "noapic" on boot ?
next parent reply other threads:[~2002-04-10 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b5926afe75.afe75b5926@water.pku.edu.cn>
2002-04-10 12:54 ` Philippe Amelant [this message]
2002-04-10 13:21 ` how to balance interrupts between 2 CPUs? lm0re
2002-04-10 14:06 ` Tim Kay
2002-04-10 14:14 ` Terje Eggestad
2002-04-10 14:31 ` Martin J. Bligh
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=1018443294.6396.10.camel@avior \
--to=pamelant@linux-at-business.com \
--cc=linux-kernel@vger.kernel.org \
/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.