From: Andi Kleen <ak@muc.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Alternative patching for prefetches & cleanup
Date: Sun, 27 Apr 2003 05:27:13 +0200 [thread overview]
Message-ID: <20030427052713.19557@colin.muc.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0304262021190.25498-100000@home.transmeta.com>; from Linus Torvalds on Sun, Apr 27, 2003 at 05:22:58AM +0200
On Sun, Apr 27, 2003 at 05:22:58AM +0200, Linus Torvalds wrote:
>
> On Sun, 27 Apr 2003, Andi Kleen wrote:
> >
> > Hmm. I thought using the Fibonaci sequence for this was clever :-)
>
> That's not the fibonacci sequence, that's just a regular sigma(i)
> (i=1..n) sequence. And if you were to generate the sequence numbers at
> compile-time I might agree with you, if you also were to avoid using
> inline asms.
True %)
The real reason I did it was to avoid having two sets of macros - one
with .byte 0x... and another with string "\x..\x..."
Now it needs duplication.
-Andi
next prev parent reply other threads:[~2003-04-27 3:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 2:19 [PATCH] Alternative patching for prefetches & cleanup Andi Kleen
2003-04-27 3:09 ` Linus Torvalds
2003-04-27 3:14 ` Andi Kleen
2003-04-27 3:22 ` Linus Torvalds
2003-04-27 3:27 ` Andi Kleen [this message]
2003-04-27 3:32 ` William Lee Irwin III
2003-04-27 8:50 ` Rene Herman
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=20030427052713.19557@colin.muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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