From: Folkert van Heusden <folkert@vanheusden.com>
To: linux-kernel@vger.kernel.org
Subject: optimalisation for strlcpy (lib/string.c)
Date: Sun, 10 Dec 2006 22:23:51 +0100 [thread overview]
Message-ID: <20061210212350.GC30197@vanheusden.com> (raw)
Hi,
Like the other patch (by that other person), I think it is faster to not
do a strlen first.
E.g. replace this:
ize_t strlcpy(char *dest, const char *src, size_t size)
{
size_t ret = strlen(src);
if (size) {
size_t len = (ret >= size) ? size - 1 : ret;
memcpy(dest, src, len);
dest[len] = '\0';
}
return ret;
}
by this:
size_t strlcpy(char *dest, const char *src, size_t size)
{
char *tmp = dest;
for(;;)
{
*dest = *src;
if (!*src)
break;
if (--size == 0)
break;
dest++;
src++;
}
*dest = 0x00;
return dest - tmp;
}
patch:
diff -uNrBbd lib/string.c string-new.c
--- lib/string.c 2006-11-04 02:33:58.000000000 +0100
+++ string-new.c 2006-12-10 22:22:08.000000000 +0100
@@ -121,14 +121,24 @@
*/
size_t strlcpy(char *dest, const char *src, size_t size)
{
- size_t ret = strlen(src);
+ char *tmp = dest;
- if (size) {
- size_t len = (ret >= size) ? size - 1 : ret;
- memcpy(dest, src, len);
- dest[len] = '\0';
+ for(;;)
+ {
+ *dest = *src;
+ if (!*src)
+ break;
+
+ if (--size == 0)
+ break;
+
+ dest++;
+ src++;
}
- return ret;
+
+ *dest = 0x00;
+
+ return dest - tmp;
}
EXPORT_SYMBOL(strlcpy);
#endif
I've tested the speed difference with this:
http://www.vanheusden.com/misc/kernel-strlcpy-opt-test.c
and the speed difference is quite a bit on a P4: 28% faster.
Signed-off by: Folkert van Heusden <folkert@vanheusden.com>
Folkert van Heusden
--
www.vanheusden.com/multitail - multitail is tail on steroids. multiple
windows, filtering, coloring, anything you can think of
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next reply other threads:[~2006-12-10 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 21:23 Folkert van Heusden [this message]
2006-12-10 21:49 ` optimalisation for strlcpy (lib/string.c) Eyal Lebedinsky
2006-12-10 22:03 ` Folkert van Heusden
2006-12-10 21:55 ` Mitchell Blank Jr
2006-12-10 21:41 ` Folkert van Heusden
2006-12-10 23:13 ` Adrian Bunk
2006-12-11 5:26 ` Clemens Koller
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=20061210212350.GC30197@vanheusden.com \
--to=folkert@vanheusden.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