From: "Dan Gora" <dan.gora@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PCI Bursting with PIO
Date: Fri, 15 Feb 2008 10:00:28 -0800 [thread overview]
Message-ID: <4779de450802151000o2c06df0fq6d0daa22c43b935b@mail.gmail.com> (raw)
In-Reply-To: <20080215130244.780285cf@core>
On Fri, Feb 15, 2008 at 5:02 AM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > Is there any way to get PIO to burst over the PCI bus in the read and
> > write direction? My device has 4 BAR registers, but the area where I
>
> I think you are doign about as well as the X folks did when they spent
> time on trying to optimise pio transfers to and from graphics card RAM.
>
That's good to know. Do you have a link or anything to their
discussion or some key words that I could hunt it down?
>
> > Any ideas would be really appreciated,
>
> Put a DMA controller on it ;)
Ugh.. sadly that's what's coming. I really don't get why the
northbridge cannot burst however. If the memory is mapped
prefetchable and you have to do a PCI read through 3 PCIe bridges to
finally get to your device it seems like it would _really_ behoove the
bridge to do a Memory read multiple and get the whole cache line. I
have searched around a lot and there doesn't seem to be any info at
all on how you can persuade these bridges to do different PCI commands
or burst. I don't know why....
thanks again for your help,
dan
next prev parent reply other threads:[~2008-02-15 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 3:28 Dan Gora
2008-02-15 10:54 ` Andi Kleen
2008-02-15 17:55 ` Dan Gora
2008-02-15 13:02 ` Alan Cox
2008-02-15 18:00 ` Dan Gora [this message]
2008-02-15 18:41 ` H. Peter Anvin
2008-02-15 19:00 ` Alan Cox
[not found] <fa.Mbzb1/2dWnp5V/5ElzijlkAstZU@ifi.uio.no>
2008-02-16 6:00 ` Robert Hancock
2008-02-17 4:53 ` Dan Gora
[not found] <fa.QF1nJvJhMpLvtquNDa6sbADHwhs@ifi.uio.no>
[not found] ` <fa.LrKLA2l3F3abMpHk4aDjFfwzFVI@ifi.uio.no>
[not found] ` <fa.kFanAY/O5VMnSf6YXqEyxmsR62U@ifi.uio.no>
2008-02-17 19:06 ` Robert Hancock
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=4779de450802151000o2c06df0fq6d0daa22c43b935b@mail.gmail.com \
--to=dan.gora@gmail.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®