From: Jeffrey Chen <cpthk@hotmail.com>
To: Philippe Proulx <eeppeliteloop@gmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: LTTng buffer mode
Date: Fri, 19 Feb 2016 09:00:34 +0000 [thread overview]
Message-ID: <BY2PR15MB07598F61A09D22D0CBF9B785ABA00__43718.3839538649$1455872507$gmane$org@BY2PR15MB0759.namprd15.prod.outlook.com> (raw)
In-Reply-To: <CAB4xu_1qu7ezjfafSHc_CmM=YzcNhu9Oxyim=kd7N2U-OTJwZw@mail.gmail.com>
Thanks.
If we make changes to LTTng to add this feature, would it violate the LTTng design principle in any way? Thanks.
________________________________________
From: Philippe Proulx <eeppeliteloop@gmail.com>
Sent: Tuesday, February 16, 2016 5:02 PM
To: Jeffrey Chen
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] LTTng buffer mode
No you cannot.
There's no hidden global buffering scheme option for user space tracing.
From the LTTng documentation:
> In the user space tracing domain, two buffering schemes are available
> when creating a channel:
>
> Per-PID buffering: keep one ring buffer per process.
> Per-UID buffering: keep one ring buffer for all processes of a single user.
and:
> The Linux kernel tracing domain only has one available buffering scheme
> which is to use a single ring buffer for the whole system.
Phil
On Tue, Feb 16, 2016 at 7:55 PM, Jeffrey Chen <cpthk@hotmail.com> wrote:
> Hi LTTng community:
>
>
> I have a question about LTTng buffer mode. According to documentation, LTTng
> supports 2 buffer modes, per-pid, and per-uid. Is there any mode to have a
> global buffer that does not have separate buffers? The reason I asked is
> because, LTTng writes different buffer traces to different directory/file.
> It is much more difficult for us to post-process separate directories. We
> would like to have all traces write into one single buffer and
> directory/file, so it is easier to do post-processing. Thanks.
>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
next prev parent reply other threads:[~2016-02-19 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BY2PR15MB0759C952513EFB6E18812650ABAE0@BY2PR15MB0759.namprd15.prod.outlook.com>
2016-02-17 1:02 ` LTTng buffer mode Philippe Proulx
[not found] ` <CAB4xu_1qu7ezjfafSHc_CmM=YzcNhu9Oxyim=kd7N2U-OTJwZw@mail.gmail.com>
2016-02-19 9:00 ` Jeffrey Chen [this message]
[not found] ` <BY2PR15MB07598F61A09D22D0CBF9B785ABA00@BY2PR15MB0759.namprd15.prod.outlook.com>
2016-02-20 18:17 ` Mathieu Desnoyers
[not found] ` <829984174.3472.1455992223842.JavaMail.zimbra@efficios.com>
2016-02-26 9:12 ` syed zaidi
[not found] ` <CAD6O9aryfG_Wh39620c2K_CVB8Oi0ZaVnQbYzGdRq1b1WMEDbQ@mail.gmail.com>
2016-02-26 18:07 ` Mathieu Desnoyers
2016-02-17 0:55 Jeffrey Chen
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='BY2PR15MB07598F61A09D22D0CBF9B785ABA00__43718.3839538649$1455872507$gmane$org@BY2PR15MB0759.namprd15.prod.outlook.com' \
--to=cpthk@hotmail.com \
--cc=eeppeliteloop@gmail.com \
--cc=lttng-dev@lists.lttng.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.