From: Arjan van de Ven <arjanv@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: ak@muc.de
Subject: Re: [PATCH] Runtime memory barrier patching
Date: 22 Apr 2003 10:43:58 +0200 [thread overview]
Message-ID: <1051001038.1419.3.camel@laptop.fenrus.com> (raw)
In-Reply-To: <200304220111.h3M1BEp5004047@hera.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On Tue, 2003-04-22 at 01:23, Linux Kernel Mailing List wrote:
> ChangeSet 1.1169, 2003/04/21 16:23:20-07:00, ak@muc.de
>
> [PATCH] Runtime memory barrier patching
>
> This implements automatic code patching of memory barriers based
> on the CPU capabilities. Normally lock ; addl $0,(%esp) barriers
> are used, but these are a bit slow on the Pentium 4.
>
very nice. Question: would it be doable use this for prefetch() as well?
Eg default to a non-prefetch kernel and patch in the proper prefetch
instruction for the current cpu ? (eg AMD prefetch vs Intel one etc etc)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2003-04-22 8:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304220111.h3M1BEp5004047@hera.kernel.org>
2003-04-22 8:43 ` Arjan van de Ven [this message]
2003-04-22 11:18 ` Andi Kleen
2003-04-22 16:11 ` Dave Jones
2003-04-22 10:12 Chuck Ebbert
-- strict thread matches above, loose matches on Subject: below --
2003-04-21 23:41 Chuck Ebbert
2003-04-22 0:04 ` Jamie Lokier
2003-04-21 19:27 Andi Kleen
2003-04-21 19:59 ` Linus Torvalds
2003-04-21 20:53 ` Andi Kleen
2003-04-21 21:04 ` Linus Torvalds
2003-04-21 21:43 ` Ulrich Drepper
2003-04-21 22:05 ` Linus Torvalds
2003-04-21 22:45 ` Andi Kleen
2003-04-21 22:11 ` Andi Kleen
2003-04-21 22:23 ` Linus Torvalds
2003-04-21 22:59 ` Andi Kleen
2003-04-21 23:35 ` Jamie Lokier
2003-04-21 23:46 ` Andi Kleen
2003-04-21 23:57 ` Jamie Lokier
2003-04-22 0:06 ` Linus Torvalds
2003-04-22 0:13 ` Jamie Lokier
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=1051001038.1419.3.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=ak@muc.de \
--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®