From: Michael Gruner via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] sink.ctf.fs vs bt_ctf_writer
Date: Mon, 24 Aug 2020 15:21:51 -0600 [thread overview]
Message-ID: <96422055-7592-4024-897D-35CD4D4211B9@ridgerun.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1135 bytes --]
Hi all
I’m integrating CTF support to a third party framework. To do so, I decided to go with the Babeltrace 2 API (I love the rewrite BTW). So basically I made my custom plug-in and the framework spawns the following processing graph:
My Framework -> SOURCE.MYPLUGIN.MYCOMPONENT -> SINK.CTF.FS
This effectively generates a valid set of CTF traces. However, when exploring the Babeltrace2 source I found the existence of a bt_ctf_writer, which seems like a convenience object to write CTF directly (without the need of the graph). This would’ve been a much simpler approach for my use case, so I’m evaluating to rewrite using bt_ctf_writer in favor of simplicity and maintainability. My questions are:
Should bt_ctf_writer be used?
bt_ctf_writer is not documented, is it because is being deprecated?
Seems like sink.ctf.fs performs the trace and metadata write back to disk when it receives the end message, whereas with bt_ctf_writer I can manually flush them (which is very convenient to me). Is there a way to achieve this using the graph?
Thanks!
Michael
www.ridgerun.com <http://www.ridgerun.com/>
[-- Attachment #1.2: Type: text/html, Size: 1842 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:[~2020-08-24 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 21:21 Michael Gruner via lttng-dev [this message]
2020-08-24 22:33 ` Philippe Proulx 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=96422055-7592-4024-897D-35CD4D4211B9@ridgerun.com \
--to=lttng-dev@lists.lttng.org \
--cc=michael.gruner@ridgerun.com \
--subject='Re: [lttng-dev] sink.ctf.fs vs bt_ctf_writer' \
/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
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).