mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Arthur Perry <kernel@linuxfarms.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Celistica with AMD chip-set
Date: Mon, 30 Aug 2004 13:17:47 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0408301306020.22149@chaos> (raw)
In-Reply-To: <Pine.LNX.4.58.0408301052030.23343@tiamat.perryconsulting.net>

On Mon, 30 Aug 2004, Arthur Perry wrote:

> Hello Alan and Richard,
>
> I have to advise caution here, as it is currently unconfirmed whether or
> not the PCI bridge configuration is "incorrect", and that it has "very
> poor PCI performance".

The crapiest 33MHz, 32-bit PCI/Bus in lowly '486 machines hanging
around the lab will beat the Celistia hands-down.

> Unless everyone in the whole wide world is setting this value and we are
> the only ones who are not, I find it hard to believe that this statement
> is not overspeculative.
>

Really?  Well somebody from Salem New Hampshire wrote email to
one of my zillions of managers claiming that this was the "fix".

I was forced to make this "fix" and it "fixed" it. Further,
every "^!&@*$%^!_*(@" so called software, hardware, and whatever
"Engineer......" If that's the correct word, required (demanded)
to see the source code because they were "sure" that " had screwed
up.

To date, there has been no such finding of screw-ups on my part.
FYI, it's really difficult to screw up a "(@#%^P_*!@&#" DMA!

Other machines are able to DMA at over 130 megabytes/second. The
boxes in question run at only 50 megabytes/second.

> The proper place for this should be in the BIOS, if it is indeed a true
> optimization point.
> But until that is positively identified, we should not assume that
> applying this globally for everyone is the right thing to do.
> As in any assumed optimization for a simgle case, it could potentially
> cause performance degradation in somebody else's HBA.
>

Not so.

> This is a cache optimization.
>
> Have you considered the possibility of this "optimization" causing a
> performance hit with Mellanox's PCI implementation?
>

I published a "fix" for the abysimal PCI performance on that
piece of crap. If you don't like it then so what. Fix the
damn box.

> What about people who have already tailored their device driver to work
> well in on this chipset and currently use "read multiple" rather than
> "read cacheline". This optimization could potentially cause a slight
> degradation of performance for them.
>

I don't give a damn.  The box has no DMA capability as it is.
One might as well just use a wet string top communicate with
the PCI boards. The "fix" forced upon me by you guys is now
somehow incorrect?

Go to hell.

>
> Arthur Perry
> Linux Systems/Software Architect
> Lead Linux Engineer
> CSU Validation Group
> Celestica, Salem, NH
> aperry@celestica.com
>


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.


  parent reply	other threads:[~2004-08-30 17:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2004-08-30 18:13       ` Arthur Perry
     [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
2004-08-30 17:45       ` Andi Kleen

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.0408301306020.22149@chaos \
    --to=root@chaos.analogic.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kernel@linuxfarms.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 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®