All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roel Kluin <12o3l@tiscali.nl>
To: David Howells <dhowells@redhat.com>
Cc: Adrian Bunk <bunk@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	cbe-oss-dev@ozlabs.org, linuxppc-dev@ozlabs.org,
	Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Willy Tarreau <w@1wt.eu>, Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH 1/3] Fix Unlikely(x) == y
Date: Mon, 18 Feb 2008 15:59:48 +0100	[thread overview]
Message-ID: <47B99D64.3090103@tiscali.nl> (raw)
In-Reply-To: <12131.1203344830@redhat.com>

David Howells wrote:
> Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> wrote:
> 
>> Hence shouldn't we ask the gcc people what's the purpose of
>> __builtin_expect(), if it doesn't live up to its promise?
> 
> __builtin_expect() is useful on FRV where you _have_ to give each branch and
> conditional branch instruction a measure of probability whether the branch
> will be taken.
> 
> David

I was wondering whether some of the uses of likely illustrated below are
incorrect or not useful.

x = likely(X) || Y

for ( ... ; likely(...); ... )

while ( likely(X) )

if ( unlikely(X) &&/|| likely(Y) )

if ( X &&/|| unlikely(Y) ) 

return likely(X);

return likely(X) ? a : b;

WARNING: multiple messages have this Message-ID (diff)
From: Roel Kluin <12o3l@tiscali.nl>
To: David Howells <dhowells@redhat.com>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Adrian Bunk <bunk@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	cbe-oss-dev@ozlabs.org, linuxppc-dev@ozlabs.org,
	Willy Tarreau <w@1wt.eu>, Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH 1/3] Fix Unlikely(x) == y
Date: Mon, 18 Feb 2008 15:59:48 +0100	[thread overview]
Message-ID: <47B99D64.3090103@tiscali.nl> (raw)
In-Reply-To: <12131.1203344830@redhat.com>

David Howells wrote:
> Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> wrote:
> 
>> Hence shouldn't we ask the gcc people what's the purpose of
>> __builtin_expect(), if it doesn't live up to its promise?
> 
> __builtin_expect() is useful on FRV where you _have_ to give each branch and
> conditional branch instruction a measure of probability whether the branch
> will be taken.
> 
> David

I was wondering whether some of the uses of likely illustrated below are
incorrect or not useful.

x = likely(X) || Y

for ( ... ; likely(...); ... )

while ( likely(X) )

if ( unlikely(X) &&/|| likely(Y) )

if ( X &&/|| unlikely(Y) ) 

return likely(X);

return likely(X) ? a : b;

  reply	other threads:[~2008-02-18 14:59 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 16:08 [PATCH 1/3] Fix Unlikely(x) == y Roel Kluin
2008-02-16 17:25 ` Arjan van de Ven
2008-02-16 17:25   ` Arjan van de Ven
2008-02-16 17:33   ` Willy Tarreau
2008-02-16 17:33     ` Willy Tarreau
2008-02-16 17:42     ` Arjan van de Ven
2008-02-16 17:42       ` Arjan van de Ven
2008-02-16 17:58       ` Willy Tarreau
2008-02-16 17:58         ` Willy Tarreau
2008-02-16 18:29         ` Arjan van de Ven
2008-02-16 18:29           ` Arjan van de Ven
2008-02-17  9:45         ` [Cbe-oss-dev] " Andrew Pinski
2008-02-17  9:45           ` Andrew Pinski
2008-02-17 10:08           ` Willy Tarreau
2008-02-17 10:08             ` Willy Tarreau
2008-02-16 18:31       ` Geoff Levand
2008-02-16 18:31         ` Geoff Levand
2008-02-16 18:39         ` Arjan van de Ven
2008-02-16 18:39           ` Arjan van de Ven
2008-02-17 11:50           ` Michael Ellerman
2008-02-17 11:50             ` Michael Ellerman
2008-02-18 13:56             ` Adrian Bunk
2008-02-18 13:56               ` Adrian Bunk
2008-02-18 14:01               ` Geert Uytterhoeven
2008-02-18 14:01                 ` Geert Uytterhoeven
2008-02-18 14:13                 ` Adrian Bunk
2008-02-18 14:13                   ` Adrian Bunk
2008-02-18 21:46                   ` Michael Ellerman
2008-02-18 21:46                     ` Michael Ellerman
2008-02-19  7:43                     ` Adrian Bunk
2008-02-19  7:43                       ` Adrian Bunk
2008-02-18 14:27                 ` David Howells
2008-02-18 14:27                   ` David Howells
2008-02-18 14:59                   ` Roel Kluin [this message]
2008-02-18 14:59                     ` Roel Kluin
2008-02-18 18:11                   ` Valdis.Kletnieks
2008-02-18 18:11                     ` Valdis.Kletnieks
2008-02-18 18:33                     ` Arjan van de Ven
2008-02-18 18:33                       ` Arjan van de Ven
2008-02-18 19:22                 ` [Cbe-oss-dev] " Andrew Pinski
2008-02-18 14:39       ` Andi Kleen
2008-02-18 14:39         ` Andi Kleen
2008-02-19  2:33         ` Nick Piggin
2008-02-19  2:33           ` Nick Piggin
2008-02-19  2:40           ` Arjan van de Ven
2008-02-19  2:40             ` Arjan van de Ven
2008-02-19  4:41             ` Nick Piggin
2008-02-19  4:41               ` Nick Piggin
2008-02-19  5:58           ` Willy Tarreau
2008-02-19  5:58             ` Willy Tarreau
2008-02-19  6:20             ` Nick Piggin
2008-02-19  6:20               ` Nick Piggin
2008-02-19  9:28             ` Andi Kleen
2008-02-19  9:28               ` Andi Kleen
2008-02-20  7:32               ` Willy Tarreau
2008-02-20  7:32                 ` Willy Tarreau
2008-02-19  9:25           ` Andi Kleen
2008-02-19  9:25             ` Andi Kleen
2008-02-19  9:46             ` Nick Piggin
2008-02-19  9:46               ` Nick Piggin
2008-02-19  9:57               ` Andi Kleen
2008-02-19  9:57                 ` Andi Kleen
2008-02-19 22:25                 ` Nick Piggin
2008-02-19 22:25                   ` Nick Piggin
2008-02-16 18:41 ` Geoff Levand

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=47B99D64.3090103@tiscali.nl \
    --to=12o3l@tiscali.nl \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=arjan@infradead.org \
    --cc=bunk@kernel.org \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=w@1wt.eu \
    /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.