DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Adel Belkhiri <adel.belkhiri@gmail.com>
Cc: dev@dpdk.org, jerinj@marvell.com, skori@marvell.com
Subject: Re: When the trace buffers are saved to disk?
Date: Fri, 29 Nov 2024 12:44:52 +0100	[thread overview]
Message-ID: <9370936.CDJkKcVGEf@thomas> (raw)
In-Reply-To: <CAMxxxdOT7JgNsT7=ubTyjUm02Ne7Fbt+1YnaCf8oXg3S+3mCng@mail.gmail.com>

28/11/2024 20:17, Adel Belkhiri:
> 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 is rte_trace_save()

> it also automatically save when the buffer becomes full?

No, DPDK is not doing such thing without user agreement.

> 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?

Yes you get it right.

> Thank you for clarifying this point.

Thanks for asking.

If you think the doc below is not clear enough,
do not hesitate to submit a patch to make the doc better:

	https://doc.dpdk.org/guides/prog_guide/trace_lib.html




      reply	other threads:[~2024-11-29 11:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 19:17 Adel Belkhiri
2024-11-29 11:44 ` Thomas Monjalon [this message]

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=9370936.CDJkKcVGEf@thomas \
    --to=thomas@monjalon.net \
    --cc=adel.belkhiri@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=skori@marvell.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;
as well as URLs for NNTP newsgroup(s).