From: "H. Peter Anvin" <hpa@zytor.com>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: Arjan van de Ven <arjan@infradead.org>,
Nick Piggin <npiggin@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: LFENCE instruction
Date: Tue, 16 Oct 2007 08:42:15 -0700 [thread overview]
Message-ID: <4714DBD7.7080706@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710161205160.1315@artax.karlin.mff.cuni.cz>
Mikulas Patocka wrote:
> On Mon, 15 Oct 2007, H. Peter Anvin wrote:
>
>> Mikulas Patocka wrote:
>>> I know about unordered stores (movnti & similar) --- they basically use
>>> write-combining method on memory that is normally write-back --- and they
>>> need sfence. But which one instruction does unordered load and needs
>>> lefence?
>>>
>> PREFETCHNTA.
>
> PREFETCH* doesn't change program semantics. The processor is allowed to
> ignore prefetch instruction if it doesn't have resources needed for
> prefetch. It not ordered wrt. fences.
>
> PREFETCHNTA was implemented as prefetch into L1 cache and omitting L2
> cache on Pentium 3 and M --- and it is implemented as prefetch into L2
> cache on other --- do it doesn't really use any special buffers.
>
It's semantics allows it to, though. It's not clear to me whether it is
actually necessary on existing chips.
It does, I believe, way-restricted prefetch on existing silicon.
-hpa
next prev parent reply other threads:[~2007-10-16 15:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 20:47 LFENCE instruction (was: [rfc][patch 3/3] x86: optimise barriers) Mikulas Patocka
2007-10-15 21:37 ` Arjan van de Ven
2007-10-15 22:08 ` Mikulas Patocka
2007-10-16 0:11 ` H. Peter Anvin
2007-10-16 10:17 ` Mikulas Patocka
2007-10-16 15:42 ` H. Peter Anvin [this message]
2007-10-16 21:25 ` LFENCE instruction Mikulas Patocka
2007-10-16 0:22 ` LFENCE instruction (was: [rfc][patch 3/3] x86: optimise barriers) Nick Piggin
2007-10-16 10:33 ` Mikulas Patocka
2007-10-16 22:29 ` Nick Piggin
2007-10-16 23:05 ` Mikulas Patocka
2007-10-16 23:21 ` Nick Piggin
2007-10-17 0:30 ` Mikulas Patocka
2007-10-17 12:24 ` Nick Piggin
2007-10-18 17:06 ` Mikulas Patocka
2007-10-17 5:51 ` Herbert Xu
2007-10-17 12:28 ` Nick Piggin
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=4714DBD7.7080706@zytor.com \
--to=hpa@zytor.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=npiggin@suse.de \
/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