From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Craig Christophel <merlin@transgeek.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: likely/unlikely
Date: Wed, 16 Jan 2002 04:14:57 -0500 [thread overview]
Message-ID: <3C454491.CA18D4AE@mandrakesoft.com> (raw)
In-Reply-To: <20020116032300.AAA27749@shell.webmaster.com@whenever> <3C450C4A.8A8382A6@mandrakesoft.com> <20020116113143.C99F8B581@smtp.transgeek.com>
Craig Christophel wrote:
>
> > likely/unlikely set the branch prediction values to 99% or 1%
>
> So all of the BUG() routines in the kernel would benifit greatly from this.
It's likely :) I would put one unlikely() in the definition of BUG_ON,
rather rather touching all the code that calls BUG(), though.
Jeff
--
Jeff Garzik | Alternate titles for LOTR:
Building 1024 | Fast Times at Uruk-Hai
MandrakeSoft | The Took, the Elf, His Daughter and Her Lover
| Samwise Gamgee: International Hobbit of Mystery
next prev parent reply other threads:[~2002-01-16 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 3:22 likely/unlikely David Schwartz
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 ` Jeff Garzik [this message]
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=3C454491.CA18D4AE@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=merlin@transgeek.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 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.