public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] optimize 64-by-32 ddivision for constant divisors on 32-bit machines
Date: Thu, 19 Nov 2015 17:28:20 +0100	[thread overview]
Message-ID: <3830931.6tMHPeiNRU@wuerfel> (raw)
In-Reply-To: <alpine.LFD.2.20.1511161710270.5826@knanqh.ubzr>

On Monday 16 November 2015 20:20:38 Nicolas Pitre wrote:
> Arnd,
> 
> Please pull the following branch:
> 
> 	git://git.linaro.org/people/nicolas.pitre/linux div64
> 
> This contains those patches I've initially posted here:
> 
> 	https://lkml.org/lkml/2015/11/2/715
> 
> Only changes to those posted patches are cosmetic improvements such as 
> the use of ilog2() replacing the custom __div64_ffs(). Exposure in 
> linux-next would be a good thing.
> 
> I also included fixes for a couple do_div() misuses that an allyesconfig 
> build turned up after switching ARM to the generic do_div() code.  
> Those patches have been posted separately and addressed to relevant 
> maintainers. They are included here until/unless those maintainers 
> include those patches in their tree.
> 
> Original cover letter:
> 
> This is a generalization of the optimization I produced for ARM a decade
> ago to turn constant divisors into a multiplication by the divisor
> reciprocal. Turns out that after all those years gcc is still not
> optimizing things on its own for that case.
> 
> This has important performance benefits as discussed in this thread:
> 
> 	https://lkml.org/lkml/2015/10/28/851
> 
> This series brings the formerly ARM-only optimization to all 32-bit
> architectures using C code by default.  The possibility for the actual
> multiplication to be implemented in assembly is provided in order to get
> optimal code.  The ARM version can be used as an example implementation
> for other interested architectures to implement.
> 

Pulled into my asm-generic tree now, it should show up in linux-next
tomorrow.

Thanks,

	Arnd

  parent reply	other threads:[~2015-11-19 16:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  1:20 [GIT PULL] optimize 64-by-32 ddivision for constant divisors on 32-bit machines Nicolas Pitre
2015-11-17  1:20 ` Nicolas Pitre
2015-11-19 16:28 ` Arnd Bergmann [this message]
2015-11-19 16:28   ` Arnd Bergmann
2015-11-20  0:29   ` Nicolas Pitre
2015-11-20 12:27     ` Arnd Bergmann
2015-11-20 13:24       ` Nicolas Pitre
2015-11-20 13:24         ` Nicolas Pitre
2015-11-22 22:18 ` Arnd Bergmann
2015-11-22 22:18   ` Arnd Bergmann
2015-11-22 22:28   ` Nicolas Pitre
2015-11-23  7:59     ` Arnd Bergmann
2015-11-23 14:59       ` Nicolas Pitre
2015-11-23 14:59         ` Nicolas Pitre
2015-11-23 16:04         ` Nicolas Pitre
2015-11-23 16:11           ` Arnd Bergmann
2015-11-23 16:11             ` Arnd Bergmann
2015-11-23 16:38             ` Nicolas Pitre
2015-11-24  5:37             ` Nicolas Pitre
2015-11-24 13:28               ` Arnd Bergmann
2015-11-24 13:28                 ` Arnd Bergmann
2015-11-24 16:44                 ` Nicolas Pitre

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=3830931.6tMHPeiNRU@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nicolas.pitre@linaro.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