linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: David Miller <davem@davemloft.net>,
	James.Bottomley@hansenpartnership.com, geert@linux-m68k.org,
	linux-arch@vger.kernel.org
Subject: Re: Arch maintainers Ahoy!
Date: Thu, 24 May 2012 08:53:20 -0700	[thread overview]
Message-ID: <CA+55aFzwZ3mCeALQx7fXX_HO4GZF03q4gtZOFGmdWkJrvwjrJg@mail.gmail.com> (raw)
In-Reply-To: <32064.1337852416@redhat.com>

On Thu, May 24, 2012 at 2:40 AM, David Howells <dhowells@redhat.com> wrote:
>
> Could you use cpu_to_be32/64() and then ffs()?  That ought to work for both
> variants of endianness.  The cpu_to_beXX() should be a noop on BE and is
> likely to be a single instruction on LE.  The meat of ffs() is usually a
> single instruction, though it may have to have zero-detect logic added.

First off, the *last* thing you want to do is go to big-endian mode.
All the bit counting gets *much* more complicated, and your argument
that it's "free" on some architectures is pointless, since it is only
free on the architectures that have the *least* users.

Secondly, it's not "likely a single instruction" on LE, neither is
ffs. It can be, but it's often one of the slower instructions.

Many architectures will have - but only in their most recent uarch
versions - popcount or similar, and if you're little-endian, that
would be what you want. Except we already figured out faster versions
for little-endian based on multiplication or a few add/shift
operations.

                        Linus

  reply	other threads:[~2012-05-24 15:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 16:50 Arch maintainers Ahoy! (was Re: x86: faster strncpy_from_user()) Linus Torvalds
2012-05-23  5:46 ` Arch maintainers Ahoy! David Miller
2012-05-23  8:02   ` Geert Uytterhoeven
2012-05-23  9:40     ` James Bottomley
2012-05-23 15:15       ` Linus Torvalds
2012-05-23 17:21         ` David Miller
2012-05-23 17:32           ` Linus Torvalds
2012-05-23 18:16             ` David Miller
2012-05-23 18:27               ` Linus Torvalds
2012-05-23 18:35                 ` David Miller
2012-05-23 18:44                   ` Linus Torvalds
2012-05-23 18:46                   ` Linus Torvalds
2012-05-23 20:36                     ` David Miller
2012-05-23 21:01                       ` Linus Torvalds
2012-05-24  2:11                         ` David Miller
2012-05-24  5:25                           ` Paul Mackerras
2012-05-24  5:56                             ` David Miller
2012-05-24  9:40               ` David Howells
2012-05-24 15:53                 ` Linus Torvalds [this message]
2012-06-13 11:08                   ` Michael Cree
2012-06-13 14:51                     ` Linus Torvalds
2012-05-24 16:45                 ` David Howells
2012-05-24 16:56                   ` Linus Torvalds
2012-05-24 17:16                   ` David Howells
2012-05-23 17:19       ` David Miller

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=CA+55aFzwZ3mCeALQx7fXX_HO4GZF03q4gtZOFGmdWkJrvwjrJg@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-arch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).