From: Manfred Spraul <manfred@colorfullife.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
linux-kernel@vger.kernel.org,
Sean Cavanaugh <seanc@gearboxsoftware.com>
Subject: Re: P4 SMP load balancing
Date: Fri, 12 Oct 2001 20:38:37 +0200 [thread overview]
Message-ID: <3BC738AD.A0329BBF@colorfullife.com> (raw)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
> > ovendev:~# cat /proc/interrupts
> > CPU0 CPU1
> > 0: 6348212 0 IO-APIC-edge timer
> > 1: 2 0 IO-APIC-edge keyboard
> > 2: 0 0 XT-PIC cascade
> > 8: 1 0 IO-APIC-edge rtc
> > 9: 0 0 IO-APIC-edge acpi
> > 16: 92620 0 IO-APIC-level eth0
> > 18: 5085 0 IO-APIC-level aic7xxx, aic7xxx
> > NMI: 0 0
> > LOC: 6348388 6348427
> > ERR: 0
> > MIS: 0
>
> I don't think this should happen. In the event of both procs having equal
> priority (linux never changes them, so they always do), we should fall back
> to the arbitration priority of the lapic. Whether you have 1 or 2 I/O apics
> working shouldn't make a difference.
The P 4 has a new apic, and lowest priority delivery doesn't work
anymore.
<<<<<<< Chapter 7.6.10 of 24547202.pdf
In operating systems that use the lowest priority interrupt delivery
mode
but do not update the TPR, the TPR information saved in the chipset will
potentially cause the interrupt to be always delivered to the same
processor from the logical set. This behavior is functionally backward
compatible with the P6 family processor but may result in unexpected
performance implications.
<<<<<<< (search for 245472 on google for the pdf file)
--
Manfred
next reply other threads:[~2001-10-12 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 18:38 Manfred Spraul [this message]
2001-10-12 21:38 ` P4 SMP load balancing Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 9:28 Sean Cavanaugh
2001-10-12 17:59 ` Martin J. Bligh
2001-10-14 9:07 ` Sean Cavanaugh
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=3BC738AD.A0329BBF@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanc@gearboxsoftware.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