From: Andi Kleen <ak@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: "Dong Feng" <middle.fengdong@gmail.com>,
"Christoph Lameter" <clameter@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: Unnecessary Relocation Hiding?
Date: Fri, 25 Aug 2006 09:38:06 +0200 [thread overview]
Message-ID: <200608250938.06240.ak@suse.de> (raw)
In-Reply-To: <17646.42148.880959.99796@cargo.ozlabs.ibm.com>
On Friday 25 August 2006 09:20, Paul Mackerras wrote:
> Andi Kleen writes:
>
> > Best is to avoid undefined behaviour in new code.
>
> Of course. But do you have a way to implement per_cpu() without it?
I was describing the ideal, not the practical reality.
-Andi
prev parent reply other threads:[~2006-08-25 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 12:00 Unnecessary Relocation Hiding? Dong Feng
2006-08-23 12:25 ` Dong Feng
2006-08-24 18:26 ` Christoph Lameter
2006-08-24 19:24 ` Andi Kleen
2006-08-24 23:31 ` Paul Mackerras
2006-08-25 1:30 ` Dong Feng
2006-08-25 3:49 ` Paul Mackerras
[not found] ` <a2ebde260608242329r12259e0k7e798ee1d8737d68@mail.gmail.com>
2006-08-25 6:39 ` Fwd: " Dong Feng
2006-08-25 6:18 ` Andi Kleen
2006-08-25 7:20 ` Paul Mackerras
2006-08-25 7:38 ` Andi Kleen [this message]
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=200608250938.06240.ak@suse.de \
--to=ak@suse.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=middle.fengdong@gmail.com \
--cc=paulus@samba.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 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.