Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: laijs@cn.fujitsu.com (Lai Jiangshan)
Subject: [ltt-dev] sub roadmap for text output
Date: Wed, 10 Dec 2008 12:55:12 +0800	[thread overview]
Message-ID: <493F4BB0.5070706@cn.fujitsu.com> (raw)


1) Marker ID management
   Marker ID identify every type of event,
   a) ASCII text output needs get name&fmt from eID faster.
   b) Marker ID and its data must be permanent.

2) ltt-relay events traveling
   current ltt-relay does not support iterator. it seems that ltt-relay is too
   complex to do this things. Is any plan to revise ltt-relay?

3) event reader
   get significative binary data from event. and convert them to a va_list
   or other type. binary in event is raw data, we must know its meaning for
   formating.

4) event text formator
   format data to text.

5) create files for text output and control

In all, I think text output is urgency for lttng, but
"ltt-relay events traveling" is the bottleneck.

Lai.





             reply	other threads:[~2008-12-10  4:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10  4:55 Lai Jiangshan [this message]
2008-12-10 12:22 ` Mathieu Desnoyers
2008-12-11  6:44   ` Lai Jiangshan
2008-12-26  9:50 ` Lai Jiangshan
2008-12-26 15:23   ` Mathieu Desnoyers

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=493F4BB0.5070706@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.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