From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, Kees Cook <keescook@chromium.org>,
Eryu Guan <eguan@redhat.com>,
Alexander Potapenko <glider@google.com>,
Chris Metcalf <metcalf@alum.mit.edu>,
David Laight <David.Laight@ACULAB.COM>,
Dmitry Vyukov <dvyukov@google.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH] lib/strscpy: remove word-at-a-time optimization.
Date: Wed, 24 Jan 2018 09:54:09 +0100 [thread overview]
Message-ID: <e6de0ec1-c59c-fea4-0335-4c5609e21656@prevas.dk> (raw)
In-Reply-To: <50fcfba8-fc16-b4a1-d117-24ebbe959c0c@virtuozzo.com>
On 2018-01-09 17:47, Andrey Ryabinin wrote:
> Attached user space program I used to see the difference.
> Usage:
> gcc -02 -o strscpy strscpy_test.c
> ./strscpy {b|w} src_str_len count
>
> src_str_len - length of source string in between 1-4096
> count - how many strscpy() to execute.
>
> Also I've noticed something strange. I'm not sure why, but certain
> src_len values (e.g. 30) drives branch predictor crazy causing worse than usual results
> for byte-at-a-time copy:
I see something similar, but at the 30->31 transition, and the
branch-misses remain at 1-3% for higher values, until 42 where it drops
back to 0%. Anyway, I highly doubt we do a lot of string copies of
strings longer then 32.
$ perf stat ./strscpy_test b 30 10000000
Performance counter stats for './strscpy_test b 30 10000000':
156,777082 task-clock (msec) # 0,999 CPUs
utilized
0 context-switches # 0,000 K/sec
0 cpu-migrations # 0,000 K/sec
48 page-faults # 0,306 K/sec
584.646.177 cycles # 3,729 GHz
<not supported> stalled-cycles-frontend
<not supported> stalled-cycles-backend
2.580.599.614 instructions # 4,41 insns per
cycle
660.114.283 branches # 4210,528 M/sec
4.891 branch-misses # 0,00% of all
branches
0,156970910 seconds time elapsed
$ perf stat ./strscpy_test b 31 10000000
Performance counter stats for './strscpy_test b 31 10000000':
258,533250 task-clock (msec) # 0,999 CPUs
utilized
0 context-switches # 0,000 K/sec
0 cpu-migrations # 0,000 K/sec
50 page-faults # 0,193 K/sec
965.505.138 cycles # 3,735 GHz
<not supported> stalled-cycles-frontend
<not supported> stalled-cycles-backend
2.660.773.463 instructions # 2,76 insns per
cycle
680.141.051 branches # 2630,768 M/sec
19.150.367 branch-misses # 2,82% of all
branches
0,258725192 seconds time elapsed
Rasmus
next prev parent reply other threads:[~2018-01-24 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 16:37 Andrey Ryabinin
2018-01-09 16:47 ` Andrey Ryabinin
2018-01-24 8:54 ` Rasmus Villemoes [this message]
2018-01-24 17:52 ` Linus Torvalds
2018-01-25 8:32 ` Dmitry Vyukov
2018-01-25 8:42 ` David Laight
2018-01-25 9:08 ` Dmitry Vyukov
2018-01-25 17:55 ` Linus Torvalds
2018-01-25 19:13 ` Andrey Ryabinin
2018-01-30 9:12 ` Dmitry Vyukov
2018-01-24 8:47 ` Rasmus Villemoes
2018-01-24 15:53 ` Andy Shevchenko
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=e6de0ec1-c59c-fea4-0335-4c5609e21656@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=David.Laight@ACULAB.COM \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=eguan@redhat.com \
--cc=glider@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metcalf@alum.mit.edu \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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®