From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Andi Kleen <ak@muc.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, mark.langsdorf@amd.com
Subject: Re: Celistica with AMD chip-set
Date: Mon, 30 Aug 2004 13:20:31 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0408301318290.22149@chaos> (raw)
In-Reply-To: <m34qmktzlk.fsf@averell.firstfloor.org>
On Mon, 30 Aug 2004, Andi Kleen wrote:
> Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> > On Llu, 2004-08-30 at 15:02, Richard B. Johnson wrote:
> >> Hello all,
> >>
> >> The Celistica server with the AMD chip-set has very poor
> >> PCI performance with Linux (and probably W$ too).
> >>
> >> The problem was traced to incorrect bridge configuration
> >> in the HyperTransport(tm) chips that connect up pairs
> >> of slots.
>
> > while((pdev = pci_find_device(0x1022, 0x7450, pdev)) != NULL)
> > pci_write_config_dword(pdev, 0x4c, 0x2ec1);
>
>
> > Can you get Celestica to mail me their PCI subvendor
> > id/devid's for the problem configuration or DMI strings
> > and then we can do a PCI quirk properly for this.
>
> Celistica is just the contract manufacturer for the AMD
> reference design, they're really AMD designs. 0122/7450
> is the AMD 8131 PCI-X bridge.
>
> I doubt it is a good idea to blindly change the configuration of the
> bridge like this in the kernel. It is probably better to wait for an
> BIOS update or if you really need an urgent fix to do it from user
> space. Any fix should probably read/change bit/write the register, not
> blindly overwrite.
>
> -Andi
>
It is NOT "blindly" overwritten. We know what was in that register
(0x2c01).
Also, it is a "fix" for those who are getting crappy performance
from their boxes. Hopefully a new BIOS will be out with more
permanent fixes.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-08-30 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2yV1c-29L-7@gated-at.bofh.it>
[not found] ` <2yVb1-2ft-57@gated-at.bofh.it>
2004-08-30 15:28 ` Andi Kleen
2004-08-30 17:20 ` Richard B. Johnson [this message]
2004-08-30 17:45 ` Andi Kleen
2004-08-30 14:02 Richard B. Johnson
2004-08-30 13:15 ` Alan Cox
2004-08-30 15:04 ` Arthur Perry
2004-08-30 15:34 ` Arthur Perry
2004-08-30 17:26 ` Richard B. Johnson
2004-08-30 17:17 ` Richard B. Johnson
2004-08-30 18:13 ` Arthur Perry
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=Pine.LNX.4.53.0408301318290.22149@chaos \
--to=root@chaos.analogic.com \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.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
all inboxes | Powered by JetHome®