From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Borislav Petkov <bp@alien8.de>, Eric Dumazet <eric.dumazet@gmail.com>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
netdev@vger.kernel.org, dborkman@redhat.com,
linux-kernel@vger.kernel.org, darkjames-ws@darkjames.pl
Subject: Re: [PATCH RFC] reciprocal_divide: correction/update of the algorithm
Date: Tue, 14 Jan 2014 21:51:43 -0500 [thread overview]
Message-ID: <52D5F7BF.7090407@gmail.com> (raw)
In-Reply-To: <20140114232538.GD29887@pd.tnic>
On 01/14/2014 06:25 PM, Borislav Petkov wrote:
> On Tue, Jan 14, 2014 at 02:45:37PM -0800, Eric Dumazet wrote:
>> Even on a Jaguar, the proposed alternative
> I don't know what Jaguar you guys are talking about but the Jaguar
> I know - Fam16h - has an int hardware divider:
>
> http://developer.amd.com/wordpress/media/2012/10/SOG_16h_52128_PUB_Rev1_1.pdf
>
> So all that talk about microcode is plain wrong. The hardware divider
> comes from Llano (F12h) so it must be some other Jaguar, maybe Bobcat.
>
> :-)
>
> If it is Bobcat, then it has a 1-bit per cycle ucode int divider.
>
Apologies, it does have a hardware divider, however it still only gets 2
bits per cycle.
next prev parent reply other threads:[~2014-01-15 2:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 21:42 [PATCH RFC] reciprocal_divide: correction/update of the algorithm Hannes Frederic Sowa
2014-01-14 18:02 ` Randy Dunlap
2014-01-15 15:02 ` Hannes Frederic Sowa
2014-01-14 18:07 ` Eric Dumazet
2014-01-14 19:22 ` Austin S Hemmelgarn
2014-01-14 19:50 ` Eric Dumazet
2014-01-14 20:10 ` Hannes Frederic Sowa
2014-01-14 20:53 ` Austin S Hemmelgarn
2014-01-14 22:45 ` Eric Dumazet
2014-01-14 23:25 ` Borislav Petkov
2014-01-15 2:51 ` Austin S. Hemmelgarn [this message]
2014-01-14 22:39 ` Hannes Frederic Sowa
2014-01-15 7:02 ` [PATCH net] bpf: do not use reciprocal divide Eric Dumazet
2014-01-15 7:28 ` David Miller
2014-01-15 7:39 ` Eric Dumazet
2014-01-15 8:00 ` Heiko Carstens
2014-01-15 8:13 ` Martin Schwidefsky
2014-01-15 10:51 ` Heiko Carstens
2014-01-15 14:21 ` Eric Dumazet
2014-01-15 14:25 ` Eric Dumazet
2014-01-15 14:50 ` [PATCH v2 " Eric Dumazet
2014-01-15 15:10 ` Matt Evans
2014-01-15 16:09 ` Eric Dumazet
2014-01-16 1:02 ` David Miller
2014-01-17 8:59 ` Heiko Carstens
2014-01-18 2:56 ` David Miller
2014-01-18 10:12 ` Heiko Carstens
2014-01-15 15:35 ` [PATCH " Martin Schwidefsky
2014-01-15 15:26 ` Martin Schwidefsky
2014-01-15 16:07 ` Eric Dumazet
2014-01-15 14:16 ` Eric Dumazet
2014-01-15 15:10 ` Heiko Carstens
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=52D5F7BF.7090407@gmail.com \
--to=ahferroin7@gmail.com \
--cc=bp@alien8.de \
--cc=darkjames-ws@darkjames.pl \
--cc=dborkman@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).