From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, mpn@google.com, vda.linux@googlemail.com
Cc: hughd@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] lib: vsprintf: Optimize put_dec_trunc8
Date: 25 Sep 2012 07:44:25 -0400 [thread overview]
Message-ID: <20120925114425.15269.qmail@science.horizon.com> (raw)
In-Reply-To: <20120924134939.23197.qmail@science.horizon.com>
Thanks to Denys Vlasenko for sending me his benchmarking code.
I went and hacked on it to ransomize the numbers being converted more,
since repeatedly converting the same number underestimates the number
of branch mispredictions.
Then I tried computing the number of digits beforehand, as mentioned
in my earlier message, and it came out slightly slower. The code is:
static noinline_for_stack
char *put_dec_trunc8(char *buf, unsigned n)
{
static unsigned const pow10[9] = { 0, 10, 100, 1000, 10000, 100000,
1000000, 10000000, 100000000 };
unsigned digits = (19 * fls(n) + 6) >> 6; /* Valid for < 44 bits */
unsigned t;
/*
* "Digits" is an estimate, always exact or high by 1, of the
* number of decimal digits in r. It is offset by 1, so digits=0
* means 1 digit. Given that the largest value ever passed to
* this function has 27 bits, The largest value is (19 * 27 +
* 6) >> 6 = 8, meaning 9 digits. However, that will always be
* rounded down because r is less than pow10[8] = 10^8.
*
* We could use smaller multipliers in cases 4 through 6, but that
* would require a shift by less than 32, which is awkward on a
* 32-bit processor and wastes more time than the larger multiply.
*/
switch (digits - (n < pow10[digits])) {
default:
__builtin_unreachable();
case 7: /* q <= 99999999 */
t = n + '0';
n = (n * (uint64_t)0x1999999a) >> 32;
*buf++ = t - 10*n;
case 6: /* q <= 9999999 */
t = n + '0';
n = (n * (uint64_t)0x1999999a) >> 32;
*buf++ = t - 10*n;
case 5: /* t <= 999999 */
t = n + '0';
n = (n * (uint64_t)0x1999999a) >> 32;
*buf++ = t - 10*n;
case 4: /* t <= 99999 */
t = n + '0';
n = (n * (uint64_t)0x1999999a) >> 32;
*buf++ = t - 10*n;
case 3: /* t <= 9999 */
t = n + '0';
n = (n * 0x199a) >> 16;
*buf++ = t - 10*n;
case 2: /* t <= 999 */
t = n + '0';
n = (n * 0xcd) >> 11;
*buf++ = t - 10*n;
case 1: /* t <= 99 */
t = n + '0';
n = (n * 0xcd) >> 11;
*buf++ = t - 10*n;
case 0: /* t <= 9 */
*buf++ = n + '0';
}
return buf;
}
But! With more extensive refactoring of the number() code, computing
the number of digits at the beginning can eliminate the entire business
of formatting into tmp[] and copying backward. We'll first compute the
number of digits, check for buffer overflow, insert the printf padding,
and then call the number-formatting code, passing the number of digits in.
It seems plausible that the resultant simplification will produce a
speedup.
I'm going to experiment with that. Denys, since I'm playing in your sandbox,
do you have any violent objections to that? (Assuming, of course, that it's
a net speed win and my surgery to function signatures isn't too hideous.)
next prev parent reply other threads:[~2012-09-25 11:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 5:21 [PATCH 1/4] lib: vsprintf: Optimize division by 10 for small integers George Spelvin
2012-08-03 5:21 ` [PATCH 2/4] lib: vsprintf: Optimize division by 10000 George Spelvin
2012-09-23 17:30 ` Michal Nazarewicz
2012-09-24 12:16 ` George Spelvin
2012-09-24 12:41 ` Michal Nazarewicz
2012-09-24 13:56 ` George Spelvin
2012-09-24 15:14 ` Geert Uytterhoeven
2012-09-24 15:48 ` George Spelvin
2012-09-24 9:03 ` Denys Vlasenko
2012-09-24 12:35 ` George Spelvin
2012-09-24 15:02 ` Denys Vlasenko
2012-08-03 5:21 ` [PATCH 3/4] lib: vsprintf: Optimize put_dec_trunc8 George Spelvin
2012-09-23 14:18 ` Rabin Vincent
2012-09-24 11:13 ` George Spelvin
2012-09-24 14:33 ` George Spelvin
2012-09-24 14:53 ` Michal Nazarewicz
2012-09-24 14:57 ` Michal Nazarewicz
2012-09-23 18:22 ` Michal Nazarewicz
2012-09-24 11:46 ` George Spelvin
2012-09-24 12:29 ` Michal Nazarewicz
2012-09-24 13:49 ` George Spelvin
2012-09-24 15:06 ` Michal Nazarewicz
2012-09-25 11:44 ` George Spelvin [this message]
2012-09-25 13:00 ` Denys Vlasenko
2012-08-03 5:21 ` [PATCH 4/4] lib: vsprintf: Fix broken comments George Spelvin
2012-09-23 17:22 ` [PATCH 1/4] lib: vsprintf: Optimize division by 10 for small integers Michal Nazarewicz
2012-09-24 14:18 ` George Spelvin
2012-09-24 9:06 ` Denys Vlasenko
2012-09-24 11:27 ` George Spelvin
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=20120925114425.15269.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpn@google.com \
--cc=vda.linux@googlemail.com \
/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
all inboxes | Powered by JetHome®