From: Fredrik Gustafsson <iveqy@iveqy.com>
To: linux-kernel@vger.kernel.org
Subject: hex_to_bin speedup
Date: Thu, 27 May 2010 12:07:29 +0200 [thread overview]
Message-ID: <20100527100729.GA21454@iveqy.com> (raw)
Hi,
I looked a bit at the newly added hex_to_bin function in lib/hexdump.c.
I do believe this is a speedup (at least according to my benchmark[1]).
However in the comments to commit
903788892ea0fc7fcaf7e8e5fac9a77379fc215b you can read
"[akpm@linux-foundation.org: use tolower(), saving 3 bytes, test the more common case first - it's quicker]"
I don't know the change that akpm has done, so I'm unsure if there's any
problems that I miss with my patch.
--
iveqy
[1] Benchmark
#include <sys/time.h>
#include <stdio.h>
int main()
{
struct timeval start, end;
int i,itr;
itr = 100000;
char c = 'A';
time_t diff;
gettimeofday(&start,NULL);
for(i = 0; i < itr; i++) {
if((c >= 'A') && (c <= 'F')) {}
}
gettimeofday(&end,NULL);
diff = end.tv_usec - start.tv_usec;
printf("if-statement: %d ms\n",diff);
gettimeofday(&start,NULL);
for(i = 0; i < itr; i++) {
c = tolower(c);
}
gettimeofday(&end,NULL);
diff = end.tv_usec - start.tv_usec;
printf("tolower(): %d ms\n",diff);
}
[2] Patch
This is faster (at least on i686).
---
lib/hexdump.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/lib/hexdump.c b/lib/hexdump.c
index 5d7a480..f01d11c 100644
--- a/lib/hexdump.c
+++ b/lib/hexdump.c
@@ -26,9 +26,10 @@ int hex_to_bin(char ch)
{
if ((ch >= '0') && (ch <= '9'))
return ch - '0';
- ch = tolower(ch);
if ((ch >= 'a') && (ch <= 'f'))
return ch - 'a' + 10;
+ if ((ch >= 'A') && (ch <= 'F'))
+ return ch - 'A' + 10;
return -1;
}
EXPORT_SYMBOL(hex_to_bin);
next reply other threads:[~2010-05-27 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 10:07 Fredrik Gustafsson [this message]
[not found] ` <AANLkTinn7aEv0ueW4uRN06XdUbEltTfmjRXEABMRN-7e@mail.gmail.com>
[not found] ` <20100527142848.GA23543@iveqy.com>
2010-05-27 16:35 ` hex_to_bin speedup Andy Shevchenko
2010-05-28 21:05 ` Fredrik Gustafsson
-- strict thread matches above, loose matches on Subject: below --
2010-05-28 21:38 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=20100527100729.GA21454@iveqy.com \
--to=iveqy@iveqy.com \
--cc=linux-kernel@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