From: Akhil Veeraghanta via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] lttng-ust on arm64 getting bogged down by the getcpu syscall (taking more than 600ns per call)
Date: Tue, 11 Oct 2022 20:57:56 +0000 [thread overview]
Message-ID: <CO1PR03MB59371096D2E4AB93558EA072E5239@CO1PR03MB5937.namprd03.prod.outlook.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 529 bytes --]
Hello!
I've run into an issue with getcpu not having a vsdo implementation and taking anywhere from 600ns to 80us (avg 1 us) when using lttng-ust tracepoints.
I am on lttng v2.13 and kernel version 4.9.253-l4t, running on a jetson (arm64). I was digging around and found that rseq might be the recommended next step
I am wondering:
1. Are there examples of using rseq system call to replace getcpu
2. Are there any existing patches that I can apply to get better getcpu performance
Thanks in advance,
Akhil
[-- Attachment #1.2: Type: text/html, Size: 1357 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2022-10-11 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 20:57 Akhil Veeraghanta via lttng-dev [this message]
2022-10-12 9:19 ` Jérémie Galarneau via lttng-dev
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=CO1PR03MB59371096D2E4AB93558EA072E5239@CO1PR03MB5937.namprd03.prod.outlook.com \
--to=lttng-dev@lists.lttng.org \
--cc=akhil.veeraghanta@outlook.com \
/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