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, 20 Oct 2008 11:03:53 +0800	[thread overview]
Message-ID: <A89E56E045314381B5ACD7622208ED81@zhaoleiwin> (raw)
In-Reply-To: <20081017161429.GA5696@Krystal>

Hello, Mathieu.

>> Are you means we can control each channel's (interrupt, process, ...) subbuf in future version?
>> (I think current version can only control low, med and high)
>> If this is true, maybe we need modify ltt_trace_create() before impl ltt_control.
>> 
> Yes, this is the goal.
So, IMHO, we can do it in following steps:

Step1: modify ltt_trace_create(), .etc, separate ltt_trace_create() into
  ltt_trace_setup(), ltt_set_channelsize(), ltt_set_channelnum(),
  ltt_trace_alloc(). But still use old netlink_based ltt_control to make
  it simple. 
  Although we modify ltt_set_channelsize() to support setting each channel's
  buffer, we make ltt_control.ko using old UI(only able to set low, med and
  high). So we don't need to modify other program such as user-mode lttctl.

Step2: Write a new module named ltt-channel-control.
  ( I think name of ltt-channel-control will be better than ltt-control,
    because we already have a module named ltt-marker-control. )
  ltt-channel-control is designed on debugfs, as we discussed.
  We can test it by echo XX > /mnt/debugfs/ltt/...

Step3: modify user-mode programs to support ltt-channel-control.
  We also need to modify lttctl's command arguments, to support setup each
  channel's buffer. (Are we take out -Z, -X, -V, -B, -z, -x in lttctl?)
  I haven't read source of lttv, it is necessary to modify?

B.R.
Zhaolei


  parent reply	other threads:[~2008-10-20  3:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48F733E6.9010007@cn.fujitsu.com>
2008-10-17  3:56 ` Zhaolei
2008-10-17  3:56   ` Zhaolei
2008-10-17  3:56   ` Zhaolei
     [not found]   ` <20081017042045.GB5067@Krystal>
2008-10-17  6:31     ` Zhaolei
     [not found]       ` <20081017161429.GA5696@Krystal>
2008-10-20  3:03         ` Zhaolei [this message]
     [not found]           ` <20081020031634.GA14209@Krystal>
2008-10-27  3:47             ` [ltt-dev] [PATCH] Separate ltt_trace_create() into ltt_trace_create() and ltt_trace_alloc() Zhaolei
2008-10-28 14:25               ` Mathieu Desnoyers
2008-10-29  4:04                 ` [ltt-dev] [PATCH] Separate ltt_trace_create() intoltt_trace_create() " Zhaolei

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=A89E56E045314381B5ACD7622208ED81@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