From: David Schwartz <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Subject: likely/unlikely
Date: Tue, 15 Jan 2002 19:22:59 -0800 [thread overview]
Message-ID: <20020116032300.AAA27749@shell.webmaster.com@whenever> (raw)
By the way, has anybody actually benchmarked these macros to see if they
make any difference. I did a few quick inexact benchmarks on test code and
found that in most cases there was no difference and in some cases code was
made worse.
--
David Schwartz
<davids@webmaster.com>
next reply other threads:[~2002-01-16 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 3:22 David Schwartz [this message]
2002-01-16 5:14 ` likely/unlikely Jeff Garzik
2002-01-16 6:00 ` likely/unlikely Anton Blanchard
2002-01-16 9:12 ` likely/unlikely Jeff Garzik
2002-01-16 6:32 ` likely/unlikely Craig Christophel
2002-01-16 7:38 ` likely/unlikely Adrian Bunk
2002-01-16 9:14 ` likely/unlikely Jeff Garzik
2002-01-16 9:29 ` likely/unlikely Jens Axboe
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=20020116032300.AAA27749@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--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