Sujet : Re: Architectural implications of locate mode I/O and channels
De : already5chosen (at) *nospam* yahoo.com (Michael S)
Groupes : comp.archDate : 03. Jul 2024, 19:25:50
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20240703212550.000011e8@yahoo.com>
References : 1 2 3 4 5 6 7
User-Agent : Claws Mail 4.1.1 (GTK 3.24.34; x86_64-w64-mingw32)
On Wed, 03 Jul 2024 13:34:39 -0400
EricP <
ThatWouldBeTelling@thevillage.com> wrote:
Michael S wrote:
On Wed, 03 Jul 2024 08:44:01 -0400
EricP <ThatWouldBeTelling@thevillage.com> wrote:
An alternative is each device has its own DMA controller
which is just a couple of counters.
The main cost is not counters, but bus mastering logic.
For PCI it was non-trivial cost even as late as year 2000. For
example, PLX PCI to local bus bridges with bus mastering
capability, like PCI 9080 costed non-trivially more than slave-only
9060.
PCI is a different matter. I think they shot themselves in the foot.
That is because the PCI design used FAST TTL and was ridiculously
complex and had all sorts of unnecessary optional features like
bridges.
>
Bridges were needed for the high-end. How else would you go over 4 or
5 slots with crappy edge conector of standard PCI? How else would you
go over 8-10 slots even with much much better Compact PCI connectors?
Bridges do not work very well in read direction, but in write direction
they do not impact performance at all.
To my eye the choice of FAST TTL looks wrong headed. They needed FAST
because they wanted to run at 33 MHz which is beyond LS TTL limit.
With a bus at 33 MHz and 4 bytes it superficially sounds like 133
MB/s. But 33 MHz was too fast to decode or latch the address and data,
plus it multiplexes address and data, and took 5 cycles to do a
transfer. So the bus actual data transfer rate was more like 133/5 =
26 MB/s.
But bursts work as advertaized.
We designed many boards PCI 32bx33MHz that sustained over 90 MB/s in
host memory to device direction and over 100 MB/s in device to host
memory.
Few still in produdction, although we will eventually move awayy from
this architectore for reason unrelated to system bus.
I looked into PCI bus interface chips when it first came out and there
were just *TWO* manufacturers for them on the planet, and they charged
$50,000 just to answer the phone, and you had to pay them to design a
custom chip for you even though it was supposed to be a standard
design. This all pushed the price of PCI cards way up so, for example,
an ISA bus modem card cost $50 but the exact same modem on PCI was
$250. No wonder most people stuck with ISA bus cards.
Sounds like very early days.
Whereas 74LS TTL was cheap and available from manufacturers
everywhere. I would have used 74LS TTL and done a straight 32-bit bus
with no options, multiplexed address and data to keep down the
connector pin count and cost. That could have run at 20 MHz which
leaves 50 ns for address and data decode and latch, and driven 8 bus
loads with no bridges. That gives 10 MT/s = 40 MB/s. Plus cheap and
widely available.
Pay attention that nothing of what you wrote above has anything to do
with difference between bus-mastering PCI devices and slave-only PCI
devices.
Date | Sujet | # | | Auteur |
2 Jul 24 | Architectural implications of locate mode I/O | 64 | | John Levine |
2 Jul 24 | Re: Architectural implications of locate mode I/O | 38 | | Thomas Koenig |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 17 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 6 | | Lynn Wheeler |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Terje Mathisen |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 9 | | Bill Findlay |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 8 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Bill Findlay |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 6 | | Stephen Fuld |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 5 | | MitchAlsup1 |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 4 | | John Levine |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 2 | | John Savard |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 1 | | John Savard |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 19 | | John Levine |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 9 | | Anton Ertl |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 6 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 4 | | MitchAlsup1 |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 3 | | Michael S |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | MitchAlsup1 |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Joe Pfeiffer |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Robert Swindells |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | John Levine |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 9 | | Thomas Koenig |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 8 | | MitchAlsup1 |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 7 | | Thomas Koenig |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 5 | | John Levine |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 4 | | MitchAlsup1 |
7 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 3 | | Paul A. Clayton |
7 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Lynn Wheeler |
7 Jul 24 | Re: patents, Architectural implications of locate mode I/O and channels | 1 | | John Levine |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of people who don’t understand locate mode I/O | 1 | | Lawrence D'Oliveiro |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 24 | | Joe Pfeiffer |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 21 | | John Levine |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 18 | | Lynn Wheeler |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 14 | | Stephen Fuld |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 7 | | John Levine |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 6 | | Stephen Fuld |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 5 | | John Levine |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 4 | | Stephen Fuld |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 3 | | Thomas Koenig |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 2 | | Thomas Koenig |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 5 | | Lawrence D'Oliveiro |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 4 | | Stephen Fuld |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 2 | | John Levine |
2 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
11 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | Lawrence D'Oliveiro |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | MitchAlsup1 |
6 Jul 24 | Re: Old printers, Architectural implications of locate mode I/O | 1 | | John Levine |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |