Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: eeppeliteloop@gmail.com (Philippe Proulx)
Subject: [lttng-dev] CTF 2.0 and lttng indexes
Date: Wed, 8 Apr 2015 15:44:01 -0400	[thread overview]
Message-ID: <CAB4xu_2wiicqTA8L5dg=jTC56hTHXGu33eiiJxvZ_bffe00ZNw@mail.gmail.com> (raw)
In-Reply-To: <5523E325.9010602@ericsson.com>

On Tue, Apr 7, 2015 at 10:01 AM, Matthew Khouzam
<matthew.khouzam at ericsson.com> wrote:
>
> Hi all,
>
> Will the lttng indexes or something more generic be specified in the CTF
> 2.0 spec?

Mathieu needs to confirm, but AFAIK, I don't think so.

However, here's an idea following what was proposed for the integration
of base addresses and symbol informations: use CTF events to record
the packet indexes within stream files. That is, everytime a packet is
closed by the tracer, append an event to its packet indexes stream,
following this description:

    event {
        name = "packet-index";
        fields := struct {
            typalias integer {
                size = 64;
            } := uint64_t;

            uint64_t offset; /* in bits */
            uint64_t size; /* in bits */
            uint64_t ts_begin;
            uint64_t ts_end;
        };
    };

size, ts_begin, and ts_end are actually not needed, but could be useful to
avoid reading the target stream file when searching for a packet. Since
all the "packet-index" events have the same size/alignment, a half-interval
search is possible.

So, one such stream of "packet-index" events per actual stream file...
what do you think? There are situations to consider, like the trace file
rotation feature of LTTng, in which case the packet index stream files should
follow the rotation.

BTW I think this conversation should be moved to the DiaMon ML since
it's about CTF.

Phil

>
>
> Thanks
> Matthew
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev



      reply	other threads:[~2015-04-08 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 14:01 Matthew Khouzam
2015-04-08 19:44 ` Philippe Proulx [this message]

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='CAB4xu_2wiicqTA8L5dg=jTC56hTHXGu33eiiJxvZ_bffe00ZNw@mail.gmail.com' \
    --to=eeppeliteloop@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox