From: Andi Kleen <ak@suse.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-arch@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] make spin_lock_prefetch a noop for UP
Date: Thu, 4 Aug 2005 15:10:37 +0200 [thread overview]
Message-ID: <20050804131037.GC9112@wotan.suse.de> (raw)
In-Reply-To: <42F212F4.5020609@yahoo.com.au>
On Thu, Aug 04, 2005 at 11:07:00PM +1000, Nick Piggin wrote:
> Is this any good?
>
> The counter argument would be that one might prefetch a
> spinlock in the head of a data structure, and expect
> the rest of the cacheline to be in cache as well. Though
> in that case, maybe prefetch/prefetchw should be used
> instead.
Can you describe what the supposed improvement of the patch is?
-Andi
next prev parent reply other threads:[~2005-08-04 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 13:07 [patch] make spin_lock_prefetch a noop for UP Nick Piggin
2005-08-04 13:10 ` Andi Kleen [this message]
2005-08-04 13:16 ` Nick Piggin
2005-08-04 13:25 ` Andi Kleen
2005-08-04 13:37 ` 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=20050804131037.GC9112@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=torvalds@osdl.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