From: John Smith <whalajam@gmail.com>
To: Julien Desfossez <jdesfossez@efficios.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: "lttng enable-channel --tracefile-size" bug
Date: Sat, 28 May 2016 14:59:13 -0700 [thread overview]
Message-ID: <CANgVouUbJtNjBDajia1E3+CCEg95-=tnqfzBW7ukQxQbn9N_6Q__12466.4285257042$1464631045$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <57499B75.80203@efficios.com>
[-- Attachment #1.1: Type: text/plain, Size: 1274 bytes --]
Julien,
thanks, I was mislead by the 2.7 documentation saying:
"...parameters of enable-channel are --tracefile-sizeand --tracefile-count,
which respectively limit the size of each trace file and the their count
for a given channel. "
In this case the tracefile-size option should be removed, will it become
useful in the future releases or has a more subtle use?
thanks, John
On Sat, May 28, 2016 at 6:21 AM, Julien Desfossez <jdesfossez@efficios.com>
wrote:
> > Hi,
> > it looks like for the "enable-channel" command, "tracefile-size" option
> > doesn't take effect, bellow are all the options, the resulted files have
> > the actual size the same as the size specified by subbuf-size option:
> >
> > # lttng -V
> > lttng (LTTng Trace Control) 2.7.1 - Herbe à Détourne
> >
> > $ lttng enable-channel chan_name -u -s session_name --discard
> > --num-subbuf 8
> > --subbuf-size 32M --tracefile-size 8K --tracefile-count 8
> > --buffers-pid
>
> Yes, that is the expected behaviour, we work with packets (sub-buffers),
> so the smallest unit we can store is the subbuf-size.
>
> With 2.7.3 I get this warning when I try your command:
> Warning: Tracefile size rounded up from (8192) to subbuffer size (33554432)
>
> Julien
>
[-- Attachment #1.2: Type: text/html, Size: 5463 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2016-05-28 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANgVouVswhgXmy=Dge5h2FA-7xsaJfDqOZ3=seG5dHjP=_4gmA@mail.gmail.com>
2016-05-28 13:21 ` "lttng enable-channel --tracefile-size" bug Julien Desfossez
[not found] ` <57499B75.80203@efficios.com>
2016-05-28 21:59 ` John Smith [this message]
[not found] ` <CANgVouUbJtNjBDajia1E3+CCEg95-=tnqfzBW7ukQxQbn9N_6Q@mail.gmail.com>
2016-05-29 19:48 ` Julien Desfossez
[not found] ` <574B4791.905@efficios.com>
2016-06-03 0:15 ` John Smith
[not found] ` <CANgVouUiQTn-TWVAwasG5VaO6jJbTvw+d9AqZbqjgfY4Y8iiig@mail.gmail.com>
2016-06-03 13:17 ` Julien Desfossez
2016-05-27 22:11 John Smith
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='CANgVouUbJtNjBDajia1E3+CCEg95-=tnqfzBW7ukQxQbn9N_6Q__12466.4285257042$1464631045$gmane$org@mail.gmail.com' \
--to=whalajam@gmail.com \
--cc=jdesfossez@efficios.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.