From: "Jim Hull" <jim.hull@hp.com>
To: "'Matthew Wilcox'" <willy@debian.org>,
"'Randolph Chung'" <tausq@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: RE: [parisc-linux] Re: [parisc-linux-cvs] 7300LC
Date: Mon, 26 Apr 2004 10:48:56 -0700 [thread overview]
Message-ID: <010f01c42bb6$bf5864e0$f463f40f@jh733133> (raw)
In-Reply-To: <20040426115918.GO22558@parcelfarce.linux.theplanet.co.uk>
The prefetch for read (using LDW) vs. prefetch for write (using LDD) applies
only to PA2.0 processors. PA1.1 processors (including the 7300LC), since
they're only 32-bit machines, don't implement LDD (64-bit load). For PA1.1,
there's only one kind of prefetch, using LDW.
-- Jim
HP PA-RISC/Itanium Processor Architect
> -----Original Message-----
> From: parisc-linux-bounces@lists.parisc-linux.org
> [mailto:parisc-linux-bounces@lists.parisc-linux.org] On
> Behalf Of Matthew Wilcox
> Sent: Monday, April 26, 2004 4:59 AM
> To: Randolph Chung
> Cc: Matthew Wilcox; parisc-linux@lists.parisc-linux.org
> Subject: [parisc-linux] Re: [parisc-linux-cvs] 7300LC
>
>
> On Sun, Apr 25, 2004 at 06:41:11PM -0700, Randolph Chung wrote:
> > willy, kyle found out that this doesn't work:
> >
> > > > Split out 7300LC from 7100LC and PREFETCH from PA20.
> >
> > extern inline void prefetchw(const void *addr)
> > {
> > __asm__("ldd 0(%0), %%r0" : : "r" (addr));
> > }
> >
> > on pa11 gas won't assemble the ldd insn.
> >
> > is this supposed to work for pa7300lc? if so we might have
> to rewrite
> > prefetchw to use a .word or something...
>
> It is supposed to work, yes. I gleaned this information from
> http://cpus.hp.com/technical_references/b7300lc.shtml section 2.2.4
> The 7300LC ERS (http://ftp.parisc-linux.org/docs/chips/pcxl2_ers.pdf)
> is of no help in this matter. In section 14.5, it says:
>
> Because the processor does not necessarily stall even with two cache
> misses pending, software prefetching can lead to better performance
> increases than on the PA7100LC. This is because a software prefetch,
> initiated by a load to general register 0, is not treated like a
> load miss by the data cache and therefore can be completed in the
> ``background'' by the hardware and is less likely to cause processor
> stalls.
>
> But, thinking about it, PA7300LC isn't SMP-capable. Is there any
> difference between prefetch-for-read and prefetch-for-write on a
> uniprocessor system? I don't think so. So possibly we should just
> define prefetchw to be the same as prefetch for CONFIG_PA7300LC and
> different for CONFIG_PA20. Makes sense?
>
> --
> "Next the statesmen will invent cheap lies, putting the blame upon
> the nation that is attacked, and every man will be glad of those
> conscience-soothing falsities, and will diligently study
> them, and refuse
> to examine any refutations of them; and thus he will by and
> by convince
> himself that the war is just, and will thank God for the better sleep
> he enjoys after this process of grotesque self-deception." --
> Mark Twain
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
next prev parent reply other threads:[~2004-04-26 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040419223250.7E3CE494572@palinux.hppa>
[not found] ` <20040419223444.GB18329@parcelfarce.linux.theplanet.co.uk>
2004-04-26 1:41 ` [parisc-linux] Re: [parisc-linux-cvs] 7300LC Randolph Chung
2004-04-26 2:00 ` John David Anglin
2004-04-26 11:59 ` Matthew Wilcox
2004-04-26 17:48 ` Jim Hull [this message]
2004-04-26 16:55 ` Joel Soete
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='010f01c42bb6$bf5864e0$f463f40f@jh733133' \
--to=jim.hull@hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.org \
--cc=willy@debian.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