From: Markus Elfring <Markus.Elfring@web.de>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-help@sourceware.org
Subject: Re: Checking special execution durations for the determination of mountable file systems
Date: Sun, 19 Sep 2021 16:04:11 +0200 [thread overview]
Message-ID: <d39ea998-5537-5fb7-f714-7974f4f38585@web.de> (raw)
In-Reply-To: <CAMXh4bW+oxHnLJt2tNxtAAvcVmE1E7Mg3N1co7XqycZimsn=KQ@mail.gmail.com>
> The statvfs() calls statfs() which in turn is a syscall. There is some
> memory copy involved on __internal_statvfs64(),
> but it's runtime should be negligible.
Are any test cases available for these functions?
Which impression did you get from the displayed execution durations?
> I would check with Linux perf with kernel probing enabled to see exactly
> what is happening.
I can eventually increase the tracing depth for the analysis tool “uftrace”
(if further details from Linux function calls would be really helpful
for such a clarification approach).
Regards,
Markus
next prev parent reply other threads:[~2021-09-19 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 6:40 Markus Elfring
2021-09-19 12:40 ` Adhemerval Zanella
2021-09-19 14:04 ` Markus Elfring [this message]
2021-09-20 13:16 ` Adhemerval Zanella
2021-09-20 13:24 ` Florian Weimer
2021-09-20 13:27 ` Adhemerval Zanella
2021-09-20 17:56 ` Markus Elfring
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=d39ea998-5537-5fb7-f714-7974f4f38585@web.de \
--to=markus.elfring@web.de \
--cc=adhemerval.zanella@linaro.org \
--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).