From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
Rakib Mullick <rakib.mullick@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH] x86,APIC: Detect lapic_is_integrated() once - use on and on.
Date: Fri, 22 May 2009 23:18:14 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.1.10.0905222309180.19449@ftp.linux-mips.org> (raw)
In-Reply-To: <4A170713.402@zytor.com>
On Fri, 22 May 2009, H. Peter Anvin wrote:
> > actually this change could be dangerous. I don't
> > remember if I saw mixed configuration at all but
> > I would not be that sure that we will never met it.
It is a matter of question whether this change gives any performance
benefit, but certainly it is not dangerous. What's the difference in code
generated?
Also APIC accesses cannot be cached, so access to the variable if hot in
the cache should be faster, but OTOH if cold, then main RAM access may
actually be slower as the APIC is quite closely coupled to the CPU. Have
any figures indicating performance change been obtained?
> That seems unlikely in the extreme. To the best of my knowledge, only
> 486s ever used the external APICs.
Several Pentium-based systems used external APICs (both ones built around
original P5 and ones using P54C chips), but mixed configurations were not
possible because of ICC bus/protocol incompatibility. First of all the
number of lines was different (5 vs 3)...
Maciej
next prev parent reply other threads:[~2009-05-22 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 13:31 [PATCH] x86,APIC: Detect lapic_is_integrated() once - use on and on Rakib Mullick
2009-05-22 20:02 ` Cyrill Gorcunov
2009-05-22 20:12 ` H. Peter Anvin
2009-05-22 20:21 ` Cyrill Gorcunov
2009-05-22 20:23 ` H. Peter Anvin
2009-05-22 20:30 ` Cyrill Gorcunov
2009-05-22 20:35 ` Cyrill Gorcunov
2009-05-22 20:59 ` H. Peter Anvin
2009-05-22 22:18 ` Maciej W. Rozycki [this message]
2009-05-23 13:07 ` Cyrill Gorcunov
2009-05-22 20:33 ` Thomas Gleixner
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=alpine.LFD.1.10.0905222309180.19449@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rakib.mullick@gmail.com \
--cc=yhlu.kernel@gmail.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