From: jdesfossez@efficios.com (Julien Desfossez)
Subject: [lttng-dev] status of lttng top
Date: Mon, 22 Oct 2012 14:10:01 -0400 [thread overview]
Message-ID: <50858BF9.705@efficios.com> (raw)
In-Reply-To: <7F632A9222059A42AF70FCB7965774AA20854D6F@ALA-MBB.corp.ad.wrs.com>
Hi Andrew,
On 22/10/12 07:00 AM, McDermott, Andrew wrote:
>
> Hi,
>
>> LTTngTop is still work in progress and will remain that way for a long
>> time, but the version in the PPA (or in the master branch in git) is
>> perfectly usable for offline traces (traces recorded and replayed
>> through LTTngTop).
>>
>> The "live" branch is more experimental and requires patches in both
>> Babeltrace and Lttng-tools (all documented in the README-LIVE file), but
>> it worked at the time of Plumbers, I didn't have much time since then to
>> rebase the branches.
>>
>> I am waiting for the release of Lttng-tools 2.1 (currently in RC) before
>> merging those patches. After these patches are integrated, LTTngTop will
>> be able to work live without any modifications, so directly reading
>> traces in memory shared with the tracer.
>
> Thanks for this info.
>
> Right now my interest is with the live streaming; we have a use case
> where the live streaming is really the only practical solution.
>
> Very roughly, would you expect the RC series to conclude this year, or
> (early) next year?
Just to clarify, are you interested in live network trace reading or
live in-memory reading ?
The patches I was talking about are for in-memory trace reading.
Thanks,
Julien
next prev parent reply other threads:[~2012-10-22 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 21:57 McDermott, Andrew
2012-10-09 2:20 ` Julien Desfossez
2012-10-22 11:00 ` McDermott, Andrew
2012-10-22 18:10 ` Julien Desfossez [this message]
2012-10-23 13:11 ` McDermott, Andrew
2012-10-25 18:40 ` Julien Desfossez
2012-10-26 12:40 ` McDermott, Andrew
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=50858BF9.705@efficios.com \
--to=jdesfossez@efficios.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