From: christoph <christoph@scalex86.org>
To: Anton Blanchard <anton@samba.org>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, shai@scalex86.org
Subject: Re: [PATCH] Move some variables into the "most_readonly" section??
Date: Mon, 27 Jun 2005 16:17:41 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0506271611500.10036@ScMPusgw> (raw)
In-Reply-To: <20050617135536.GB6434@krispykreme>
On Fri, 17 Jun 2005, Anton Blanchard wrote:
> > I think it would be better to first still see numbers for
> > this questionable optimizations.
>
> Agreed, it would be nice to see some benchmark numbers.
Sorry seem to have lost track of this thread of thought.
These are optimizations that try to avoid false aliasing as
a result of the linker placing hot spots into the same cacheline. These
are not predictable per se. Some future patch may rearrange variables that
then produce another case of false aliasing.
In order to demonstrate the effect, I would need to be allowed to put
some hot variables into the same cacheline. And that seem to be pointless
because we all know the outcome.
next prev parent reply other threads:[~2005-06-27 23:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 19:58 christoph
2005-06-08 13:18 ` Andi Kleen
2005-06-14 22:54 ` christoph
2005-06-14 23:04 ` Andi Kleen
2005-06-14 23:17 ` Christoph Lameter
2005-06-14 23:19 ` Andi Kleen
2005-06-14 23:27 ` Christoph Lameter
2005-06-14 23:54 ` Andi Kleen
2005-06-14 23:23 ` Andrew Morton
2005-06-14 23:46 ` christoph
2005-06-14 23:58 ` Andrew Morton
2005-06-15 0:05 ` christoph
2005-06-15 0:16 ` Andrew Morton
2005-06-15 0:41 ` Andi Kleen
2005-06-17 13:55 ` Anton Blanchard
2005-06-27 23:17 ` christoph [this message]
2005-06-15 0:18 ` 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=Pine.LNX.4.62.0506271611500.10036@ScMPusgw \
--to=christoph@scalex86.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.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®