public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: linux-kernel@vger.kernel.org,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] lib/vsprintf.c: Even faster decimal conversion
Date: Thu, 05 Mar 2015 08:03:33 -0800	[thread overview]
Message-ID: <1425571413.31859.1.camel@perches.com> (raw)
In-Reply-To: <87r3t3eafm.fsf@rasmusvillemoes.dk>

On Thu, 2015-03-05 at 16:22 +0100, Rasmus Villemoes wrote:
> On Sat, Feb 21 2015, Rasmus Villemoes <linux@rasmusvillemoes.dk> wrote:
> 
> > [...] decimal conversion [...] it does indeed seem like there is
> > something to be gained, especially on 64 bits.
> >
> > $ ./test64
> > Distribution              Function         Cycles/conv  Conv/1 sec
> > uniform([10, 2^64-1])     linux_put_dec          127.72         23047567
> > uniform([10, 2^64-1])     rv_put_dec              60.73         45932786
> >                           +/-                   -52.45%          +99.30%
> [...]
> > 3 + neg_binom(0.50)       linux_put_dec           16.85        159560933
> > 3 + neg_binom(0.50)       rv_put_dec              12.59        204607570
> >                           +/-                   -25.31%          +28.23%
> 
> I'm assuming the underwhelming response means NAK.

Dunno why you assume that, sometimes it just takes
awhile for people to look at non-critical, infrequent
optimization changes like this.

Seems sensible enough to me though.


  reply	other threads:[~2015-03-05 16:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 23:51 [RFC] lib/vsprintf.c: Even faster decimal conversion Rasmus Villemoes
2015-03-05 15:22 ` Rasmus Villemoes
2015-03-05 16:03   ` Joe Perches [this message]
2015-03-05 16:10     ` Tejun Heo
2015-03-05 22:24       ` Rasmus Villemoes
2015-03-10 10:47         ` Rasmus Villemoes
2015-03-10 12:42           ` Tejun Heo
2015-03-10 12:57             ` Rasmus Villemoes
2015-03-10 23:01               ` [PATCH v1] " Rasmus Villemoes
2015-03-11 21:52                 ` Andrew Morton
2015-03-19 21:41                   ` Rasmus Villemoes
2015-03-12 18:49                 ` Jeff Epler
2015-03-13  0:08                 ` Jeff Epler
2015-03-13  0:30                   ` Jeff Epler
2015-03-13  8:58                 ` [PATCH] lib/vsprintf.c: silence sparse warnings about decpair[] initialization Rasmus Villemoes
2015-03-19 21:44                   ` [PATCH] lib/vsprintf.c: improve put_dec_trunc8 slightly Rasmus Villemoes
2015-03-18  0:50 ` [RFC] lib/vsprintf.c: Even faster decimal conversion Denys Vlasenko
2015-03-18  0:52   ` Denys Vlasenko
2015-03-18 17:10   ` Rasmus Villemoes

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=1425571413.31859.1.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=peterz@infradead.org \
    --cc=tj@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