From: Robert Love <rml@ufl.edu>
To: Tony Hagale <tony@hagale.net>
Cc: Bulent Abali <abali@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: Pentium SSE prefetcht0 instruction... How do you make it work
Date: 27 Sep 2001 15:55:35 -0400 [thread overview]
Message-ID: <1001620540.4649.25.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.21.0109271335550.4511-100000@hagale.net>
In-Reply-To: <Pine.LNX.4.21.0109271335550.4511-100000@hagale.net>
On Thu, 2001-09-27 at 14:43, Tony Hagale wrote:
> Intel's p3/4 prefetch instructions are hints only. They are only executed
> asynchronously, and depend heavily on the other load on the processor at
> the time. They are not required to prefetch, *and* they are not required
> to be executed when you think they should in the flow of the program. You
> can serialize them by using an MFENCE instruction, but they still aren't
> guaranteed to run.
>
> Check the p4 manuals. In fact, I'm not sure prefetch was implemented in
> p3. I could be wrong, check the manual.
prefetch is in P3 and P4.
there are prefetcht0, prefetcht1, prefetcht2, and prefetchnta
instructions, Intel's programming docs have references on these all
online.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-09-27 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 18:40 Pentium SSE prefetcht0 instruction... How do you make it work Bulent Abali
2001-09-27 18:43 ` Tony Hagale
2001-09-27 19:55 ` Robert Love [this message]
2001-09-27 19:54 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-09-27 20:09 Bulent Abali
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=1001620540.4649.25.camel@phantasy \
--to=rml@ufl.edu \
--cc=abali@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@hagale.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.