archive mirror
 help / color / mirror / Atom feed
* [lttng-dev] sink.ctf.fs vs bt_ctf_writer
@ 2020-08-24 21:21 Michael Gruner via lttng-dev
  2020-08-24 22:33 ` Philippe Proulx via lttng-dev
  0 siblings, 1 reply; 2+ messages in thread
From: Michael Gruner via lttng-dev @ 2020-08-24 21:21 UTC (permalink / raw)
  To: lttng-dev

[-- 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:


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?

Michael <>

[-- Attachment #1.2: Type: text/html, Size: 1842 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

lttng-dev mailing list

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-08-24 22:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-24 21:21 [lttng-dev] sink.ctf.fs vs bt_ctf_writer Michael Gruner via lttng-dev
2020-08-24 22:33 ` Philippe Proulx via lttng-dev

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).