From: Grant Grundler <grundler@cup.hp.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: The IO problem on multiple PCI busses
Date: Fri, 02 Mar 2001 09:46:12 -0800 [thread overview]
Message-ID: <200103021746.JAA29510@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Thu, 01 Mar 2001 18:19:37 PST." <15007.825.483003.106274@pizda.ninka.net>
"David S. Miller" wrote:
> There is another case you are ignoring. Some devices support memory
> space as well as I/O space, but only operate reliably when their
> I/O space window is used to access it.
ok. Those also fall into the category of "I personally don't care" :^)
> It just sounds to me like the hppa pci controllers are crap,
> especially the GSC one.
In defense of the HW designers, Dino operates extremely well
in the environment it was designed for. Principally, workstations
with HP graphics cards (which only use MMIO). Optimizations for
graphics make it one of the fastest PCI-1X (and Cujo is PCI-2X)
HBA's - that's according to a 3rd party graphics card vendor who
has ported to the major high-end platforms.
> At least the rope one does something
> reasonable when you have a 64-bit kernel. The horrors you've told me
> about the IOMMUs and stream-caches on these chips further confirms my
> theory :-)
Yup. *sigh*. Between chip bugs, tradeoffs of performance, time to market,
and simple programming interface, things got pretty ugly (its the
old saying about "Pick any two").
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-03-02 17:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 1:22 Grant Grundler
2001-03-02 2:19 ` David S. Miller
2001-03-02 17:46 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-01 15:33 Benjamin Herrenschmidt
2001-03-01 15:41 ` Benjamin Herrenschmidt
2001-03-01 18:30 ` Alan Cox
2001-03-01 19:09 ` David S. Miller
2001-03-01 19:33 ` Dan Malek
2001-03-01 19:41 ` David S. Miller
2001-03-01 19:59 ` Dan Malek
2001-03-01 20:09 ` Benjamin Herrenschmidt
2001-03-01 20:22 ` David S. Miller
2001-03-01 20:27 ` David S. Miller
2001-03-02 11:25 ` Benjamin Herrenschmidt
2001-03-03 1:08 ` David S. Miller
2001-03-01 19:49 ` Benjamin Herrenschmidt
2001-03-01 20:21 ` David S. Miller
2001-03-01 22:26 ` Alan Cox
2001-03-02 11:20 ` Benjamin Herrenschmidt
2001-03-03 1:06 ` David S. Miller
2001-03-03 2:25 ` Benjamin Herrenschmidt
2001-03-03 11:01 ` Jeff Garzik
2001-03-03 17:28 ` Benjamin Herrenschmidt
2001-03-05 16:20 ` David Woodhouse
2001-03-06 23:01 ` Oliver Xymoron
2001-03-07 2:07 ` Tony Mantler
2001-03-05 23:21 ` Chris Wedgwood
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=200103021746.JAA29510@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.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®