From: Rocky Dunlap <rsdunlapiv@gmail.com>
To: lttng-dev@lists.lttng.org
Subject: Using Babeltrace to write CTF for MPI application
Date: Tue, 4 Apr 2017 15:29:19 -0600 [thread overview]
Message-ID: <CAK-w0DeOHsrygOt4CLVBB55edg6W+hrEzX2+A-UwFn6E14HDoQ__4204.01476226306$1491341404$gmane$org@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1316 bytes --]
I am instrumenting an MPI application to output a custom application trace
in CTF using Babeltrace 1.5.2. I would like to end up with a single trace
with multiple streams, one per process. All streams share the same stream
class (and metadata). All processes have access to the same file system. I
am using the C CTF writer API using this test as an example:
https://github.com/efficios/babeltrace/blob/stable-1.5/tests/lib/test_ctf_writer.c
What I have in mind is something like this: process 0 would be responsible
for writing the metadata and its own stream, while all other processes
would only need to write their own stream.
The issue I have run into is that the individual stream file names are
determined by appending stream->id to the stream filename and the stream id
is determined behind the scenes as stream->id =
stream_class->next_stream_id++. Since each process has its own address
space, all processes want stream id of 0.
Is there a way using the current API to explicitly set the stream id so
that each process will write to a separate file?
I'm also open for suggestions on the overall approach. The main reason to
have each process as a separate stream in a single trace is so that I can
open the entire trace in an analysis tool like TraceCompass and see all
processes together.
Rocky
[-- Attachment #1.2: Type: text/html, Size: 1573 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:[~2017-04-04 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 21:29 Rocky Dunlap [this message]
[not found] <CAK-w0DeOHsrygOt4CLVBB55edg6W+hrEzX2+A-UwFn6E14HDoQ@mail.gmail.com>
2017-04-04 23:52 ` Using Babeltrace to write CTF for MPI application Jonathan Rajotte Julien
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='CAK-w0DeOHsrygOt4CLVBB55edg6W+hrEzX2+A-UwFn6E14HDoQ__4204.01476226306$1491341404$gmane$org@mail.gmail.com' \
--to=rsdunlapiv@gmail.com \
--cc=lttng-dev@lists.lttng.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.