Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: zhaolei@cn.fujitsu.com (Zhaolei)
Subject: [ltt-dev] TODO list before releasing LTTng-buffering to LKML
Date: Mon, 27 Oct 2008 11:10:40 +0800	[thread overview]
Message-ID: <425B5523CE444FC9899AA24B51C4B4B4@zhaoleiwin> (raw)
In-Reply-To: <20081024203823.GA8197@Krystal>

* Mathieu Desnoyers <compudj at krystal.dyndns.org>wrote:
> Hi,
> 
> Thanks for the steady work those past days.
> 
> This is mainly a status update of the TODO and request for status
> feedback on the action items :
> 
> * Mathieu Desnoyers (compudj at krystal.dyndns.org) wrote:
>> * Mathieu Desnoyers (compudj at krystal.dyndns.org) wrote:
>> > Hi!
>> > 
>> > Just to keep you posted on the current development, this is what is left
>> > on my roadmap before I post a minimal LTTng (only the timestamping,
>> > event ID management and buffering) to LKML :
>> > 
>> > Todo list before posting LTTng-buffering to LKML
>> > 
>> > - Create a simplified ltt-relay (use interrupt disable instead of
>> >   lockless algo)
> 
> Done,
> 
>> > - merge a simplified lttv in lttng
> 
> Still todo,
> 
>> > 
>> > Todo list after posting first LTTng-buffering release to LKML :
>> > 
>> > - assign marker IDs per channel
> 
> Still todo,
> 
>> > - switch ltt-control.ko (currently over netlink) to debugfs
> 
>> > - switch marker list (and marker activation (currently in /proc/ltt) to debugfs
We separated it into 3 steps,
(in 2008-10-20's ltt-maillist with title of "TODO list before releasing LTTng-buffering to LKML]")
and now we have finished a phototype of step1.
It step1's src is confirmd, we will continue step2 and 3.

We will send you src of step1 today(based on 2.6.27.2-lttng-0.46).

>> >   Marker directory. One file per marker.
We will begin it soon.

>> > - Create a ltt-ascii.ko kernel module which merge-sorts the buffers and exports
>> >   them to userspace through a debugfs file.
We will begin it soon.

> 
> Being done by Fujitsu, what is the status of these items ? Do you need
> help or feedback on any of those ?
> 
> Thanks and regards,
> 
> Mathieu
> 
> -- 
> Mathieu Desnoyers
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
> 
>


  reply	other threads:[~2008-10-27  3:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08  1:02 Mathieu Desnoyers
2008-10-09  2:21 ` Mathieu Desnoyers
2008-10-24 20:38   ` Mathieu Desnoyers
2008-10-27  3:10     ` Zhaolei [this message]
2008-10-14  8:50 ` Lai Jiangshan
2008-10-14  9:17   ` Andrew McDermott

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=425B5523CE444FC9899AA24B51C4B4B4@zhaoleiwin \
    --to=zhaolei@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