From: Shuji YAMAMURA <yamamura@flab.fujitsu.co.jp>
To: jbourne@MtRoyal.AB.CA
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: SMP P4 APIC/interrupt balancing
Date: Wed, 17 Apr 2002 21:47:54 +0900 [thread overview]
Message-ID: <m3hemajxtx.wl@vivo.proc.flab.fujitsu.co.jp> (raw)
In-Reply-To: In your message of "Tue, 16 Apr 2002 16:29:32 -0600 (MDT)" <Pine.LNX.4.44.0204161535130.735-500000@skuld.mtroyal.ab.ca>
At Tue, 16 Apr 2002 16:29:32 -0600 (MDT),
James Bourne <jbourne@MtRoyal.AB.CA> wrote:
> Hi All,
> Ok, we have a Dell PE4600 with dual P4X processors. It will not balance
> interrupts between the two cpus, CPU0 always receives the bulk
> of the interrupts, although both processors are being utilized
> by processes on the system. This system is not yet in production, so I
> have some time to try things on it.
>
> Current kernel is 2.4.18 with the LSE APIC Routing patch
> (http://sourceforge.net/projects/lse). 2.4.18 stock (well ok, -rc4) has
> much the same results.
We observed the similar problem on our i860 based P4 SMP machine.
We examined several tests and got the following fact:
- Only the upper 4 bits of the task priority is effective on
Pentium 4.
The LSE APIC Routing patch assigns values from 0x10 to 0x18 to TPR for
setting task priority, that means the upper 4 bits are always '0001'.
Based on the previous obserbation, these values are useless in terms
of proper interrupt distribution.
To get an expected operation, upper 4 bits must be changed.
You may refer the following thread that talks this problem.
"P4 SMP load balancing"
http://marc.theaimsgroup.com/?t=100287923700006&r=1&w=2
Appendix.
Our experiments were examined on two different systems.
The following table shows the relations between the TPR value of each
CPU and the interrupt destination.
Pentium4 Machine:
CPU: Pentium4 Xeon 2.0GHz x 2
Motherboard: Supermicro P4DCE
Chipset: Intel860
Pentium3 Machine:
CPU: Pentium3 500MHz x 2
Motherboard: ASUS CUR-DLS
Chipset: Serverworks ServerSet3 LE
Boot Processor: CPU#0
TPR Value Interrupt CPU
CPU#0 CPU#1 Pen3 Pen4
=========================================
01 02 0or1 0
02 01 0or1 0
0f 00 0or1 0
-----------------------------------------
10 01 1 1
10 11 0 0
11 10 1 0
1f 10 1 0
11 11 0or1 0
-----------------------------------------
20 20 0or1 0
20 10 1 1
20 21 0 0
21 20 1 0
-----------------------------------------
----
Shuji YAMAMURA
Grid Computing & Bioinformatics Laboratory, FUJITSU Laboratories, LTD.
E-mail: yamamura@flab.fujitsu.co.jp
next prev parent reply other threads:[~2002-04-17 12:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 22:29 James Bourne
2002-04-17 4:43 ` Martin J. Bligh
2002-04-17 4:47 ` James Bourne
2002-04-17 14:41 ` James Bourne
2002-04-17 13:08 ` Ingo Molnar
2002-04-17 18:52 ` Steffen Persvold
2002-04-17 16:51 ` Ingo Molnar
2002-04-17 18:58 ` Steffen Persvold
2002-04-17 18:58 ` Steffen Persvold
2002-04-17 19:06 ` James Bourne
2002-04-18 8:23 ` Maciej W. Rozycki
2002-04-17 18:56 ` James Bourne
2002-04-17 17:07 ` Ingo Molnar
2002-04-17 20:02 ` James Bourne
2002-04-17 21:10 ` Hyperthreading Martin J. Bligh
2002-04-17 20:15 ` Hyperthreading Robert Love
2002-04-17 20:23 ` Hyperthreading Dave Jones
2002-04-17 21:24 ` Hyperthreading Jeff V. Merkey
2002-04-17 20:25 ` Hyperthreading James Bourne
2002-04-17 21:26 ` Hyperthreading Jeff V. Merkey
2002-04-18 0:31 ` Hyperthreading Martin J. Bligh
2002-04-18 4:50 ` Hyperthreading Jeff V. Merkey
2002-04-17 22:12 ` Hyperthreading Alan Cox
2002-04-18 16:04 ` SMP P4 APIC/interrupt balancing Bill Davidsen
2002-04-19 11:14 ` Mark Hounschell
2002-04-19 13:27 ` James Bourne
2002-04-17 12:47 ` Shuji YAMAMURA [this message]
2002-04-18 17:48 Dave Olien
2002-04-19 4:38 ` Ingo Molnar
[not found] <20020418214623.20221.qmail@patternassociates.com>
2002-04-18 22:49 ` Maciej W. Rozycki
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=m3hemajxtx.wl@vivo.proc.flab.fujitsu.co.jp \
--to=yamamura@flab.fujitsu.co.jp \
--cc=jbourne@MtRoyal.AB.CA \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®