From: Aditya Kurdunkar via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] Is it possible to disable recording the CPU id for USTs?
Date: Tue, 18 Jun 2024 18:25:50 +0530 [thread overview]
Message-ID: <CAFV=bv=hp9n8fCxxWjHn_wKQZHyAizDzVbSkVhvjNJSE_LrmEQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 755 bytes --]
Hello,
Please bear with me if this is a naive question. I am working on an
embedded ARM chip (1GB ram, 2CPUs) where I want to collect trace events for
a long duration of time. From the research that I have done (mostly reading
papers on LTTng tracing, conference talks and documentation) I have seen it
mentioned that for ARM the overhead is greater because the system call to
get the CPU is quite slow. In my use case I am okay with not having this
information. The current benchmarks show a 3 microsecond overhead of a
single tracepoint on ARM in comparison to 150ns on a x86 machine. Hence, my
question is: Is it possible to disable recording the CPU somehow? Any
suggestions for decreasing the overhead other than this are welcome.
Regards,
Aditya
[-- Attachment #1.2: Type: text/html, Size: 833 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:[~2024-06-18 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 12:55 Aditya Kurdunkar via lttng-dev [this message]
2024-06-18 14:00 ` Kienan Stewart via lttng-dev
2024-06-18 15:30 ` Kienan Stewart 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='CAFV=bv=hp9n8fCxxWjHn_wKQZHyAizDzVbSkVhvjNJSE_LrmEQ@mail.gmail.com' \
--to=lttng-dev@lists.lttng.org \
--cc=adityakurdunkar2@gmail.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