public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: linux-os@analogic.com
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	christos gentsis <christos_gentsis@yahoo.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI-X support
Date: Sat, 02 Jul 2005 00:20:47 +0200	[thread overview]
Message-ID: <m3oe9mtbgg.fsf@defiant.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0507011514570.5048@chaos.analogic.com> (Richard B. Johnson's message of "Fri, 1 Jul 2005 15:25:33 -0400 (EDT)")

"Richard B. Johnson" <linux-os@analogic.com> writes:

> Yep. The board uses a PLX PCI 9656BA chip configured for local-bus
> transfers during DMA The local-bus is 32-bits from a FIFO. There
> is no way to collapse these writes from the 32-bit source/dest.
> The transfers are 32 quadwords for a write and 16 quadwords for
> a read, but that represents a burst, not the data-width. Without
> a 64-bit data-path to memory on one side, and a 64-bit data-path
> to the device (a FIFO) on the other side, you will not get 64-bit
> transfers.

I don't know about this particular bridge, but in general you can
have 64-bit transfers over PCI(-X) corresponding to 32-bit transfers
over local bus. The local bus has to be twice as fast as PCI bus or
you won't be able to saturate PCI bus. Especially if it's the bridge
doing PCI BM DMA transfers (and not, say, another processor on the
local bus).
-- 
Krzysztof Halasa

  reply	other threads:[~2005-07-01 22:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 17:48 PCI-X support christos gentsis
2005-07-01 18:00 ` Richard B. Johnson
2005-07-01 18:05   ` christos gentsis
2005-07-01 19:02     ` Richard B. Johnson
2005-07-01 19:09       ` Vojtech Pavlik
2005-07-01 19:25         ` Richard B. Johnson
2005-07-01 22:20           ` Krzysztof Halasa [this message]
2005-07-01 18:40   ` Vojtech Pavlik
2005-07-01 19:09 ` Greg KH

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=m3oe9mtbgg.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=christos_gentsis@yahoo.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=vojtech@suse.cz \
    /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