From: "Måns Rullgård" <mans@mansr.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"shemminger\@linux-foundation.org"
<shemminger@linux-foundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vineet.Gupta1\@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"linux-snps-arc\@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"rmk+kernel\@arm.linux.org.uk" <rmk+kernel@arm.linux.org.uk>,
"davem\@davemloft.net" <davem@davemloft.net>,
"mingo\@elte.hu" <mingo@elte.hu>
Subject: Re: [PATCH] __div64_32: implement division by multiplication for 32-bit arches
Date: Fri, 30 Oct 2015 17:45:20 +0000 [thread overview]
Message-ID: <yw1xy4ekb68f.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1510301253140.630@knanqh.ubzr> (Nicolas Pitre's message of "Fri, 30 Oct 2015 12:55:38 -0400 (EDT)")
Nicolas Pitre <nicolas.pitre@linaro.org> writes:
> On Fri, 30 Oct 2015, Alexey Brodkin wrote:
>
>> Hi Nicolas,
>>
>> On Fri, 2015-10-30 at 11:17 -0400, Nicolas Pitre wrote:
>> > On Fri, 30 Oct 2015, Måns Rullgård wrote:
>> >
>> > > Nicolas Pitre <nicolas.pitre@linaro.org> writes:
>> > >
>> > > > OK... I was intrigued, so I adapted my ARM code to the generic case,
>> > > > including the overflow avoidance optimizations. Please have look and
>> > > > tell me how this works for you.
>> > > >
>> > > > If this patch is accepted upstream, then it could be possible to
>> > > > abstract only the actual multiplication part with some architecture
>> > > > specific assembly.
>> > >
>> > > Good idea.
>> >
>> > Could you please provide a reviewed-by or acked-by tag?
>>
>> Sure!
>>
>> Acked-by: Alexey Brodkin <abrodkin@synopsys.com>
>>
>> BTW I thought about that optimization a bit more and now I think
>> we may even skip addition of arch-specific assembly insertions.
>
> I'm going to do it anyway given that I already have it for ARM. It'll
> be opt-in, so if your arch doesn't provide it then the current C
> implementation will be used by default.
Great. I'll try it out on MIPS once you've posted the patch.
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2015-10-30 17:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 22:47 [PATCH] __div64_32: implement division by multiplication for 32-bit arches Alexey Brodkin
2015-10-28 23:32 ` Nicolas Pitre
2015-10-29 7:34 ` Alexey Brodkin
2015-10-30 1:26 ` Nicolas Pitre
2015-10-30 5:41 ` Vineet Gupta
2015-10-30 12:41 ` Måns Rullgård
2015-10-30 12:40 ` Måns Rullgård
2015-10-30 15:17 ` Nicolas Pitre
2015-10-30 15:54 ` Alexey Brodkin
2015-10-30 16:55 ` Nicolas Pitre
2015-10-30 17:45 ` Måns Rullgård [this message]
2015-11-04 23:46 ` Nicolas Pitre
2015-11-04 23:48 ` Nicolas Pitre
2015-11-05 3:13 ` Vineet Gupta
2015-11-05 5:06 ` Nicolas Pitre
2015-11-04 23:49 ` Måns Rullgård
2015-10-30 14:28 ` Alexey Brodkin
2015-10-29 0:36 ` kbuild test robot
2015-10-29 12:52 ` Måns Rullgård
2015-10-29 13:05 ` Alexey Brodkin
2015-10-29 13:37 ` Måns Rullgård
2015-10-29 13:31 ` Russell King - ARM Linux
2015-10-29 14:32 ` Alexey Brodkin
2015-10-29 17:09 ` Randy Dunlap
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=yw1xy4ekb68f.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mingo@elte.hu \
--cc=nicolas.pitre@linaro.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=shemminger@linux-foundation.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