[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tracecompass-dev] [lttng-dev] CTF2-PROP-1.0: Proposal for a major revision of the Common Trace Format, version 1.8
|
----- Original Message -----
> From: "Jérémie Galarneau" <jeremie.galarneau@xxxxxxxxxxxx>
> To: "Philippe Proulx" <pproulx@xxxxxxxxxxxx>
> Cc: "diamon-discuss" <diamon-discuss@xxxxxxxxxxxxxxxxxxxxxxxxx>, "lttng-dev" <lttng-dev@xxxxxxxxxxxxxxx>,
> "tracecompass-dev" <tracecompass-dev@xxxxxxxxxxx>, "etienne bergeron" <etienne.bergeron@xxxxxxxxx>, "francois doray"
> <francois.doray@xxxxxxxxx>
> Sent: Sunday, 11 December, 2016 06:13:09
> Subject: Re: [lttng-dev] CTF2-PROP-1.0: Proposal for a major revision of the Common Trace Format, version 1.8
>
> May I propose the addition of packet-begin and packet-end attributes,
> analogous to the current "timestamp_begin" and "timestamp_end" fields?
>
> These fields greatly facilitate the job of readers that need to index
> and seek within a CTF stream (time-wise) if clocks are used. Moreover,
> the attributes could be re-used shall the index format currently
> produced by LTTng become part of the official specification in one
> form or another.
>
> Thoughts?
Isn't it enough to tag the `timestamp_begin` field with
`update-data-stream-clock-now` and the `timestamp_end` field with
`update-data-stream-clock-after-packet`?
If you need to seek, read the packet header and context, then
look at the current values of the data stream clocks and at their
projected values (after packet).
Philippe Proulx
EfficiOS Inc.
http://www.efficios.com/
> Jérémie
