From: Christian Weiss <Christian.Weiss@EMEA.NEC.COM>
To: Florian Weimer <fweimer@redhat.com>
Cc: "libc-help@sourceware.org" <libc-help@sourceware.org>,
Felix Uhl <Felix.Uhl@EMEA.NEC.COM>
Subject: RE: Runtime discrepancy clock_gettime + funcition instrumentation
Date: Thu, 29 Jul 2021 08:18:31 +0000 [thread overview]
Message-ID: <c1572584122349cdbe0d0c8994613ebb@EUX13SRV2.EU.NEC.COM> (raw)
In-Reply-To: <87fsvx60f0.fsf@oldenburg.str.redhat.com>
Dear Florian,
Thank you for the quick reply. As far as I understand, I can check if vdso is used by using strace on the binary. Doing so I get:
```[cweiss@amd022 overhead]$ strace ./test_time_static_gcc.x 1 2>&1 | grep -i clock_gettime
clock_gettime(CLOCK_MONOTONIC, {tv_sec=89045, tv_nsec=95268751}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=89145, tv_nsec=95813405}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=89145, tv_nsec=95863144}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=89145, tv_nsec=95933573}) = 0
[cweiss@amd022 overhead]$ strace ./test_time_dyn_gcc.x 1 2>&1 | grep -i clock_gettime```
Am I right that this implies that vdso is not used in the static binary, but in the dynamic one? Is there a way to activate it in the static case or do I just have to live with that?
Best regards,
Christian
-----Original Message-----
From: Florian Weimer [mailto:fweimer@redhat.com]
Sent: 29 July 2021 09:32
To: Christian Weiss <Christian.Weiss@EMEA.NEC.COM>
Cc: libc-help@sourceware.org; Felix Uhl <Felix.Uhl@EMEA.NEC.COM>
Subject: Re: Runtime discrepancy clock_gettime + funcition instrumentation
* Christian Weiss:
> Measuring the runtime, the static binary takes about five times more time to finish than the dynamic one. I do not yet understand this observation:
>
> [cweiss@amd022 overhead]$ time ./test_time_static_gcc.x 10000000
> sum: 49999995000000
> real 0m2.594s
> user 0m0.396s
> sys 0m2.197s
> [cweiss@amd022 overhead]$ time ./test_time_dyn_gcc.x 10000000
> sum: 49999995000000
>
> real 0m0.518s
> user 0m0.515s
> sys 0m0.002s
Have you checked that the statically linked version uses vDSO acceleration instead of system calls?
Thanks,
Florian
Click https://www.mailcontrol.com/sr/fIQaiVcf9cfGX2PQPOmvUg0Q1FXI7Aabn0rrnrkHFzjvcdFTukB4r3gIRLMubDcYTms2r1hgqRkeq4Nrivo6iw== to report this email as spam.
next prev parent reply other threads:[~2021-07-29 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 7:26 Christian Weiss
2021-07-29 7:31 ` Florian Weimer
2021-07-29 8:18 ` Christian Weiss [this message]
2021-07-29 8:20 ` Florian Weimer
2021-07-29 8:29 ` Christian Weiss
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=c1572584122349cdbe0d0c8994613ebb@EUX13SRV2.EU.NEC.COM \
--to=christian.weiss@emea.nec.com \
--cc=Felix.Uhl@EMEA.NEC.COM \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).