From: Sultan Alsawaf <sultan@kerneltoast.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [RFCv2] string: Use faster alternatives when constant arguments are used
Date: Sat, 23 Mar 2019 19:24:06 -0700 [thread overview]
Message-ID: <20190324022406.GA18988@sultan-box.localdomain> (raw)
In-Reply-To: <20190324014445.28688-1-sultan@kerneltoast.com>
I messed up the return value for strcat in the first patch. Here's a fixed
version, ready for some scathing reviews.
From: Sultan Alsawaf <sultan@kerneltoast.com>
When strcpy, strcat, and strcmp are used with a literal string, they can
be optimized to memcpy or memcmp calls. These alternatives are faster
since knowing the length of a string argument beforehand allows
traversal through the string word at a time without being concerned
about looking for the terminating zero character. In some cases, the
replaced calls to memcpy or memcmp can even be optimized out completely
for a significant speed up.
Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
---
include/linux/string.h | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/include/linux/string.h b/include/linux/string.h
index 7927b875f..59c301c0e 100644
--- a/include/linux/string.h
+++ b/include/linux/string.h
@@ -476,4 +476,34 @@ static __always_inline size_t str_has_prefix(const char *str, const char *prefix
return strncmp(str, prefix, len) == 0 ? len : 0;
}
+/*
+ * Replace some common string helpers with faster alternatives when one of the
+ * arguments is a constant (i.e., literal string). This uses strlen instead of
+ * sizeof for calculating the string length in order to silence compiler
+ * warnings that may arise due to what the compiler thinks is incorrect sizeof
+ * usage. The strlen calls on constants are folded into scalar values at compile
+ * time, so performance is not reduced by using strlen.
+ */
+#define strcpy(dest, src) \
+ __builtin_choose_expr(__builtin_constant_p(src), \
+ memcpy((dest), (src), strlen(src) + 1), \
+ (strcpy)((dest), (src)))
+
+#define strcat(dest, src) \
+ __builtin_choose_expr(__builtin_constant_p(src), \
+ ({ \
+ memcpy(strchr((dest), '\0'), (src), strlen(src) + 1); \
+ (dest); \
+ }), \
+ (strcat)((dest), (src)))
+
+#define strcmp(dest, src) \
+ __builtin_choose_expr(__builtin_constant_p(dest), \
+ __builtin_choose_expr(__builtin_constant_p(src), \
+ (strcmp)((dest), (src)), \
+ memcmp((dest), (src), strlen(dest) + 1)), \
+ __builtin_choose_expr(__builtin_constant_p(src), \
+ memcmp((dest), (src), strlen(src) + 1), \
+ (strcmp)((dest), (src))))
+
#endif /* _LINUX_STRING_H_ */
--
2.21.0
next prev parent reply other threads:[~2019-03-24 2:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 1:44 [RFC] " Sultan Alsawaf
2019-03-24 2:24 ` Sultan Alsawaf [this message]
2019-03-24 3:31 ` [RFCv2] " Nathan Chancellor
2019-03-24 7:18 ` [RFC v3] " Sultan Alsawaf
2019-03-24 21:17 ` [RFCv2] " Rasmus Villemoes
2019-03-24 22:32 ` Sultan Alsawaf
2019-03-25 21:24 ` Rasmus Villemoes
2019-03-30 22:59 ` Sultan Alsawaf
2019-04-01 20:43 ` Rasmus Villemoes
2019-04-01 23:55 ` Sultan Alsawaf
2019-04-02 8:17 ` 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=20190324022406.GA18988@sultan-box.localdomain \
--to=sultan@kerneltoast.com \
--cc=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®