Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Joel Soete" <jsoe0708@tiscali.be>
To: "James Bottomley" <James.Bottomley@steeleye.com>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] backport bitops.h stuff
Date: Fri, 1 Aug 2003 19:09:37 +0200	[thread overview]
Message-ID: <3F29178A000004FF@ocpmta7.freegates.net> (raw)
In-Reply-To: <1059753543.2092.30.camel@mulgrave>

> Actually, this patch looks decidedly non-optimal.

> See include/linux/bitops.h:generic_ffs for how it should be done on
> architectures that don't have any machine instruction help.  That's only
> four if statements and no loop.

Yes it was like this (just a lake of #include <linux/bitops.h>) into 2.4

Why was it is changed in 2.5?

> I see we already have the loop thing in 2.5, but should we consider
> simply using the generic operations there as well?

> even for __ffs, which is just a slight optimisation over ffs, using
> generic_ffs would probably be faster

If I have time next week I can test your idea.

Thanks,
    Joel


------------------------------------------------------
Soldes Tiscali ADSL : 27,50 euros/mois jusque fin 2003.
On s'habitue vite à payer son ADSL moins cher!
Plus d'info? Cliquez ici... http://reg.tiscali.be/default.asp?lg=fr 

  reply	other threads:[~2003-08-01 17:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 15:28 [parisc-linux] backport bitops.h stuff Joel Soete
2003-08-01 15:35 ` Joel Soete
2003-08-01 15:59 ` James Bottomley
2003-08-01 17:09   ` Joel Soete [this message]
2003-08-01 17:14     ` LaMont Jones
2003-08-01 17:25       ` Joel Soete
2003-08-01 17:33       ` James Bottomley
2003-08-04 10:43       ` Joel Soete
2003-08-04 15:14         ` LaMont Jones
2003-08-04 16:08           ` James Bottomley
2003-08-04 17:04             ` Joel Soete
2003-08-04 16:53           ` Joel Soete

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=3F29178A000004FF@ocpmta7.freegates.net \
    --to=jsoe0708@tiscali.be \
    --cc=James.Bottomley@steeleye.com \
    --cc=parisc-linux@parisc-linux.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