All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org, matthew@wil.cx, davem@redhat.com
Subject: Re: When should we use likely() / unlikely() / get_unaligned() ?
Date: Mon, 09 Feb 2004 10:00:47 +1100	[thread overview]
Message-ID: <20040208230331.79FEB2C003@lists.samba.org> (raw)
In-Reply-To: Your message of "Sun, 08 Feb 2004 11:13:53 -0000." <1076238833.12587.229.camel@imladris.demon.co.uk>

In message <1076238833.12587.229.camel@imladris.demon.co.uk> you write:
> To be honest, I'm more interested in the case of get_unaligned(). The
> principle is fairly similar -- the ratio between the performance of the
> inline and the exception cases varies wildly from architecture to
> architecture. But the range is far wider -- we now support architectures
> in 2.6 where alignment fixups _cannot_ happen, and the cost of the
> 'exception' case should be considered infinite.

Um, we do?  I thought it was compulsory in the kernel, otherwise
networking breaks on packets w/ wierd hardware headers.

Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2004-02-08 23:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 11:06 When should we use likely() / unlikely() / get_unaligned() ? David Woodhouse
2004-02-08 10:43 ` Rusty Russell
2004-02-08 11:13   ` David Woodhouse
2004-02-08 23:00     ` Rusty Russell [this message]
2004-02-08 23:06       ` David Woodhouse
2004-02-08 23:11       ` David S. Miller
2004-02-08 23:14         ` David Woodhouse
2004-02-16 11:39     ` Pavel Machek

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=20040208230331.79FEB2C003@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=davem@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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.