Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] [PATCH v3] lttng: remove ltt root directory if it's	no needed
Date: Wed, 18 Feb 2009 21:38:42 -0500	[thread overview]
Message-ID: <20090219023841.GA6077@Krystal> (raw)
In-Reply-To: <20090219105750.955C.A69D9226@jp.fujitsu.com>

* KOSAKI Motohiro (kosaki.motohiro at jp.fujitsu.com) wrote:
> > We have to cleanup the lttng's root directory of debugfs if 
> > there is nobody uses it any more. Because any related lttng
> > modules are unloaded, no need to keep this directory.
> > 
> > This patch is based on 2.6.29-rc3-lttng-0.92.
> 
> hmhm. There is one meta question.
> 
> Why do we need ltt-control unloadability?
> We expect merge lttng into mainline in nearly future.
> 
> At that time, Who need ltt core kernel module (not any specific probe).
> 
> IOW, why ca't we do following?
> 

The main argument would be that on embedded systems with few memory,
some might want to leave the tracer unloaded until they need it.

Having the whole tracer available as modules makes that possible. If
it's built into the kernel, one has to leave some memory to the tracer
code and data structures even when unneeded. This is why I opted for a
fully modular design for LTTng.

> 
> config LTT_TRACE_CONTROL
> -        tristate "Linux Trace Toolkit Trace Controller"
> +        bool "Linux Trace Toolkit Trace Controller"
>         depends on LTT_TRACER
>         default m

and that would be default y :-)

Mathieu

>         help
>           If you enable this option, the debugfs-based Linux Trace Toolkit Trace
>           Controller will be either built in the kernel or as module.
> 
> 
> 
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68




  parent reply	other threads:[~2009-02-19  2:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18  8:16 [ltt-dev] [PATCH] " Gui Jianfeng
2009-02-18  8:28 ` Mathieu Desnoyers
2009-02-18  9:00   ` Gui Jianfeng
2009-02-18 11:50   ` [ltt-dev] [PATCH v2] " Gui Jianfeng
2009-02-18 23:50     ` KOSAKI Motohiro
2009-02-19  1:16       ` Gui Jianfeng
2009-02-19  1:39         ` [ltt-dev] [PATCH v3] " Gui Jianfeng
2009-02-19  2:02           ` KOSAKI Motohiro
2009-02-19  2:19             ` Gui Jianfeng
2009-02-19  2:38             ` Mathieu Desnoyers [this message]
2009-02-19  3:14           ` 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=20090219023841.GA6077@Krystal \
    --to=compudj@krystal.dyndns.org \
    /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