From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCI Burst
Date: Thu, 23 Sep 2004 21:07:59 -0600 [thread overview]
Message-ID: <003901c4a1e3$b2ae1de0$6601a8c0@northbrook> (raw)
In-Reply-To: <fa.qb32f1i.oj0poe@ifi.uio.no>
Two things that I'd check, that the memory range shows up as prefetchable
(i.e. in lspci) and also that the memory region is mapped with ioremap and
not ioremap_nocache. Also, what's the region defined as in /proc/mtrr? I
think it has to be mapped as write-back for burst reads to work. When the
CPU reads in a cache line in that memory range from the bus, that should
hopefully get passed through as a burst read on the PCI bus, but that may be
chipset-dependent.
Getting PIO-mode PCI reads and writes like this to work efficiently seems a
rather difficult thing to do..
----- Original Message -----
From: "Brian McGrew" <Brian@doubledimension.com>
Newsgroups: fa.linux.kernel
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, September 23, 2004 7:22 PM
Subject: PCI Burst
> Running RedHat 7.3 with the 2.4.20 kernel.
>
> How do I enable PCI burst mode for reading and writing on the PCI bus? We
> mmap 128MB per board that we install and now that we've added our
> addressing to the /proc/mtrr file, we can burst on write but we're not
> seeing any burst on the read.
>
> Any ideas?
>
> -brian
>
> Brian D. McGrew {brian@doubledimension.com || pacemakertaker@rock.com }
> ---
>> Failure is not an option; it is included with every Microsoft product.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2004-09-24 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.qb32f1i.oj0poe@ifi.uio.no>
2004-09-24 3:07 ` Robert Hancock [this message]
2004-09-24 0:34 Brian McGrew
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='003901c4a1e3$b2ae1de0$6601a8c0@northbrook' \
--to=hancockr@shaw.ca \
--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®