From: Adel Belkhiri <adel.belkhiri@gmail.com>
To: dev@dpdk.org
Subject: When the trace buffers are saved to disk?
Date: Thu, 28 Nov 2024 14:17:26 -0500 [thread overview]
Message-ID: <CAMxxxdOT7JgNsT7=ubTyjUm02Ne7Fbt+1YnaCf8oXg3S+3mCng@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Hi all,
Recently, while tracing applications from the apps and examples
directories, I became confused about when the trace buffer is written to
disk. Is the trace data saved only when rte_save_trace() is called, or does
it also automatically save when the buffer becomes full?
From my understanding, rte_save_trace() is invoked when the application
executes rte_eal_cleanup(). Does this mean the target application needs to
explicitly support tracing by calling rte_save_trace()—perhaps at regular
intervals—to dump the trace buffer to disk? Otherwise, will we only get a
fragment of the trace saved during rte_eal_cleanup() execution?
Thank you for clarifying this point.
Best,
Adel
[-- Attachment #2: Type: text/html, Size: 742 bytes --]
reply other threads:[~2024-11-28 19:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAMxxxdOT7JgNsT7=ubTyjUm02Ne7Fbt+1YnaCf8oXg3S+3mCng@mail.gmail.com' \
--to=adel.belkhiri@gmail.com \
--cc=dev@dpdk.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 NNTP newsgroup(s).