From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: Cache Flushes
Date: Wed, 24 Nov 1999 15:24:32 -0800 [thread overview]
Message-ID: <199911242324.PAA06000@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 24 Nov 1999 14:38:49 PST." <383C68F9.C8C6792A@hp.com>
Frank Rowand wrote:
> Philipp Rumpf wrote:
...
> > As soon as we've implemented page colouring (which turns out to be really v
> ery
> > close to large page support), I expect us to get along with very very few
> > cache flushes - basically I hope we can avoid them completely.
> >
> > Philipp Rumpf
>
> No such luck. You'll need cache flushing in drivers for non-coherent IO.
Frank is (as usual) right. Rule of thumb is if the box doesn't have an
I/O MMU (aka ccio or sba) or not using it, then it's not I/O coherent.
Every DMA transaction will require flushes/purges before or after
(inbound vs. outbound) of payload and device control data on such boxes.
My understanding is only PA2.0 supports speculative prefetching.
AFIAK that's ok since all PA2.0 boxes have an I/O MMU and the prefetched
data will be recalled/dropped during the course of the DMA.
Conclusion: In the "performance code path", PA1.1 will generally (some
PA1.1 are also I/O coherent) need flushes/purges and PA2.0 won't.
However, I wouldn't code this based on PA2.0 vs PA1.1 since the presence
of U2/Uturn/sba are what matter. And we will probably want to ignore
those chips for PA2.0 bringup (ie bringup will be not be I/O coherent).
grant
Grant Grundler
Unix Developement Lab
+1.408.447.7253
next prev parent reply other threads:[~1999-11-24 23:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-18 23:16 [parisc-linux] Progress John David Anglin
1999-11-19 3:30 ` Philipp Rumpf
1999-11-21 23:07 ` John David Anglin
1999-11-22 1:12 ` John David Anglin
1999-11-22 8:24 ` Philipp Rumpf
1999-11-22 9:59 ` Alan Cox
1999-11-22 15:54 ` Philipp Rumpf
1999-11-22 7:30 ` Philipp Rumpf
1999-11-22 18:11 ` John David Anglin
1999-11-22 18:27 ` Stan Sieler
1999-11-22 18:42 ` Philipp Rumpf
1999-11-22 18:33 ` Philipp Rumpf
1999-11-22 20:55 ` John David Anglin
1999-11-23 11:47 ` Philipp Rumpf
1999-11-23 16:19 ` John David Anglin
1999-11-23 18:03 ` Philipp Rumpf
1999-11-23 19:01 ` John David Anglin
1999-11-23 21:11 ` Stan Sieler
1999-11-24 10:00 ` Philipp Rumpf
1999-11-24 19:00 ` Stan Sieler
1999-11-24 19:33 ` Philipp Rumpf
1999-11-24 20:55 ` [parisc-linux] Progress - Update John David Anglin
1999-11-24 21:05 ` Philipp Rumpf
1999-11-24 21:27 ` Kirk Bresniker
1999-11-24 21:37 ` Philipp Rumpf
1999-11-24 22:38 ` Frank Rowand
1999-11-24 23:24 ` Grant Grundler [this message]
1999-11-25 0:31 ` John David Anglin
1999-11-25 1:17 ` Alan Cox
1999-11-25 13:24 ` Philipp Rumpf
1999-11-25 23:47 ` John David Anglin
1999-11-30 18:17 ` John David Anglin
1999-11-30 18:21 ` Alan Cox
1999-11-30 18:32 ` Philipp Rumpf
1999-11-30 19:31 ` Alan Cox
1999-11-30 20:14 ` Mark Klein
1999-11-30 23:40 ` John David Anglin
1999-12-01 15:41 ` Philipp Rumpf
1999-12-01 18:03 ` Alan Cox
1999-12-01 18:29 ` Alex deVries
1999-12-01 18:34 ` Alan Cox
1999-12-02 2:51 ` Philipp Rumpf
1999-12-01 18:33 ` John David Anglin
1999-12-01 18:54 ` Alan Cox
1999-12-01 18:55 ` Grant Grundler
1999-11-26 13:40 ` Matthew Wilcox
1999-11-23 15:59 ` [parisc-linux] Progress Paul Bame
1999-11-23 16:33 ` John David Anglin
1999-11-23 17:05 ` Paul Bame
1999-11-23 20:15 ` John David Anglin
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=199911242324.PAA06000@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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