All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: segher@kernel.crashing.org, hancockr@shaw.ca,
	lists@nerdbynature.de, linux-kernel@vger.kernel.org,
	mingo@elte.hu, tglx@linutronix.de, johnstul@us.ibm.com
Subject: Re: [PATCH] common implementation of iterative div/mod
Date: Thu, 8 May 2008 13:26:30 -0700	[thread overview]
Message-ID: <20080508132630.f4105b42.akpm@linux-foundation.org> (raw)
In-Reply-To: <48231959.4050406@goop.org>

On Thu, 08 May 2008 16:16:41 +0100
Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> We have a few instances of the open-coded iterative div/mod loop, used
> when we don't expcet the dividend to be much bigger than the divisor.
> Unfortunately modern gcc's have the tendency to strength "reduce" this
> into a full mod operation, which isn't necessarily any faster, and
> even if it were, doesn't exist if gcc implements it in libgcc.
> 
> The workaround is to put a dummy asm statement in the loop to prevent
> gcc from performing the transformation.
> 
> This patch creates a single implementation of this loop, and uses it
> to replace the open-coded versions I know about.

Fair enough.  I'll plan on feeding this into 2.6.26 soon.

>  #endif /* BITS_PER_LONG == 32 */
> +
> +/*
> + * Iterative div/mod for use when dividend is not expected to be much
> + * bigger than divisor.
> + */
> +unsigned iter_div_u64_rem(u64 dividend, u32 divisor, u64 *remainder)
> +{
> +	unsigned ret = 0;
> +
> +	while(dividend >= divisor) {
> +		/* The following asm() prevents the compiler from
> +		   optimising this loop into a modulo operation.  */
> +		asm("" : "+rm"(dividend));
> +
> +		dividend -= divisor;
> +		ret++;
> +	}
> +
> +	*remainder = dividend;
> +
> +	return ret;
> +}
> +EXPORT_SYMBOL(iter_div_u64_rem);
> 

I think it would be better to do s/unsigned/u32/ here.  It's cosmetic, but
all this sort of code is pretty formal about the sizes of the types which
it uses, and it sure needs to be.


  reply	other threads:[~2008-05-08 20:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.QTbvQYXhEm5VNP5dvkl5JG7NHYQ@ifi.uio.no>
2008-05-04 17:35 ` undefined reference to __udivdi3 (gcc-4.3) Robert Hancock
2008-05-04 22:19   ` Segher Boessenkool
2008-05-07  9:29     ` Jeremy Fitzhardinge
2008-05-08 15:16       ` [PATCH] common implementation of iterative div/mod Jeremy Fitzhardinge
2008-05-08 20:26         ` Andrew Morton [this message]
2008-05-08 22:00           ` Jeremy Fitzhardinge
2008-05-08 20:52         ` Segher Boessenkool
2008-05-08 21:57           ` Jeremy Fitzhardinge
2008-05-09 11:45         ` Christian Kujau
2008-05-14  6:46         ` Andrew Morton
2008-05-14  7:33           ` Jeremy Fitzhardinge
2008-05-14  8:33             ` Andi Kleen
2008-05-14  9:55               ` Jeremy Fitzhardinge
2008-05-14 10:50                 ` Andi Kleen
2008-05-14 10:52                   ` Jeremy Fitzhardinge
2008-05-14 11:21                     ` Andi Kleen
2008-05-14 12:58                       ` Jeremy Fitzhardinge

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=20080508132630.f4105b42.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hancockr@shaw.ca \
    --cc=jeremy@goop.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=mingo@elte.hu \
    --cc=segher@kernel.crashing.org \
    --cc=tglx@linutronix.de \
    /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.