On Fri, Jul 12, 2019 at 2:04 AM Ravindra Kumar Meena
<rmeena...@gmail.com> wrote:
>
> Hi developers,
>
> trace {
> major = 1;
> minor = 8;
> uuid = "6a7715d0-b502-4c65-8678-6777ac7f755a";
> byte_order = le;
> packet.header := struct {
> uint32_t magic;
> uint8_t uuid[16];
> uint32_t stream_id;
> uint64_t stream_instance_id;
> };
> };
>
> In the above what does stream_instance_id does? In CTF documentation [1] it
> looks like packet.header can contain three values(magic, uuid, stream_id)
> then what is stream_instance_id?
This is the ID of the stream itself, whereas `stream_id` is in fact the
ID of the class or type of stream. Many streams (one per CPU, for
example) can share the same stream class ID (`stream_id`), but have
different stream IDs (`stream_instance_id`).
In LTTng, we use the stream ID property to group different stream files
which contain data which belong to the same logical stream, in
particular when you use the trace file rotation feature. It's important
to do that because otherwise you can't know which stream file contains
which stream. There's `cpu_id` in the packet context, but that's not
specified.
When the `stream_instance_id` member does not exist, then, for a CTF
trace on the file system, each stream file implicitly represents a
different stream.
>
> Please attend this ASAP
Was that turnaround time good enough for you?
Phil
>
> Thanks
>
> --
> Ravindra Kumar Meena,
> B. Tech. Computer Science and Engineering,
> Indian Institute of Technology (Indian School of Mines), Dhanbad
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
