All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pauline Middelink <middelink@polyware.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: * 4 converted to << 2 for networking code
Date: Wed, 10 Jan 2001 17:25:05 +0100	[thread overview]
Message-ID: <20010110172505.A32188@polyware.nl> (raw)
In-Reply-To: <20010110174859.R7498@prosa.it> <3A5C778C.CFB363F3@didntduck.org> <20010110180322.T7498@prosa.it> <20010110161146.A3252@unthought.net> <20010110182546.U7498@prosa.it>
In-Reply-To: <20010110182546.U7498@prosa.it>; from antirez@invece.org on Wed, Jan 10, 2001 at 06:25:46PM +0100

On Wed, 10 Jan 2001 around 18:25:46 +0100, antirez wrote:
> On Wed, Jan 10, 2001 at 04:11:46PM +0100, Jakob ?stergaard wrote:
> > On most processors <<2 is slower than *4.   It's outright stupid to 
> > write <<2 when we mean *4 in order to optimize for one out of a
> > gazillion supported architectures - even more so when the compiler
> > for the one CPU where <<2 is faster, will actually generate a shift
> > instead of a multiply as a part of the standard optimization.
> 
> Hug, ok, so all the << 2 already in should be changed in *4.
> My point is that it is better to use only << 2 or *4, selecting
> the better form.

Well, better not change things so they look like:

#define	MSG_BLA1	(1<<1)
#define	MSG_BLA2	(1*4)
#define	MSG_BLA3	(1<<3)

as a result... :)

    Met vriendelijke groet,
        Pauline Middelink
-- 
GPG Key fingerprint = 2D5B 87A7 DDA6 0378 5DEA  BD3B 9A50 B416 E2D0 C3C2
For more details look at my website http://www.polyware.nl/~middelink
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-10 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 16:48 * 4 converted to << 2 for networking code antirez
2001-01-10 14:38 ` David S. Miller
2001-01-10 14:54 ` Brian Gerst
2001-01-10 17:03   ` antirez
2001-01-10 15:11     ` Jakob Østergaard
2001-01-10 15:18       ` Mike Harrold
2001-01-10 15:31         ` Chris Jones
2001-01-10 16:23         ` Jamie Lokier
2001-01-10 16:26           ` Mike Harrold
2001-01-10 17:25       ` antirez
2001-01-10 16:25         ` Pauline Middelink [this message]
2001-01-11  0:29       ` H. Peter Anvin
2001-01-10 22:21 ` Matthias Andree

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=20010110172505.A32188@polyware.nl \
    --to=middelink@polyware.nl \
    --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 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.