public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pavel Roskin <proski@gnu.org>, Michael Buesch <mb@bu3sch.de>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 4/7] mac80211: make ieee80211_get_hdrlen_from_skb return unsigned
Date: Mon, 09 Jun 2008 09:25:01 -0700	[thread overview]
Message-ID: <1213028701.5974.11.camel@brick> (raw)
In-Reply-To: <1213002931.698.65.camel@johannes.berg>

On Mon, 2008-06-09 at 11:15 +0200, Johannes Berg wrote:
> > unlikely() isn't some magic make-me-faster function, it just moves
> > code
> > to the end of the function to get it out of the icache and jumps to it
> > in the unlikely case it is taken.  When all there is is a return, I
> > don't think it even makes any difference.  In both these cases a
> > comment
> > is probably more appropriate.
> 
> That's not true on ppc where you can actually tell the processor about
> the jump likelyhood for its branch prediction.

I was unaware of that.

> 
> > On X86-32 at least the generated code is exactly the same with or
> > without the unlikely()s.  I'll put them back in a follow-on if people
> > are really attached to them.
> 
> Please keep them there, I think they make sense for normal operation.

Kept, will be in a v2.

Harvey


      reply	other threads:[~2008-06-09 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 17:51 [PATCH 4/7] mac80211: make ieee80211_get_hdrlen_from_skb return unsigned Harvey Harrison
2008-06-06 18:24 ` Michael Buesch
2008-06-06 18:47   ` Harvey Harrison
2008-06-06 20:15     ` Pavel Roskin
2008-06-07  2:24       ` Harvey Harrison
2008-06-09  9:15         ` Johannes Berg
2008-06-09 16:25           ` Harvey Harrison [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=1213028701.5974.11.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=proski@gnu.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