From: Julien Desfossez <jdesfossez@efficios.com>
To: John Smith <whalajam@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: "lttng enable-channel --tracefile-size" bug
Date: Sun, 29 May 2016 15:48:33 -0400 [thread overview]
Message-ID: <574B4791.905__18941.2097832703$1464551340$gmane$org@efficios.com> (raw)
In-Reply-To: <CANgVouUbJtNjBDajia1E3+CCEg95-=tnqfzBW7ukQxQbn9N_6Q@mail.gmail.com>
> Julien,
> thanks, I was mislead by the 2.7 documentation saying:
> "...parameters
> of |enable-channel| are |--tracefile-size|and |--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?
No, the tracefile-size options does what it says, the limitation is that
the smallest unit it can work with is the subbuf-size. So the smallest
tracefile size you can have is the subbuf-size.
If you are using 4k subbuffers and you limit the size of the tracefiles
to 4M, then you will have at most 1000 full packets in each tracefile.
But if you have subbuffers of 8M, the smallest tracefile size you can
have is 8M.
Julien
_______________________________________________
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-29 19:48 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
[not found] ` <CANgVouUbJtNjBDajia1E3+CCEg95-=tnqfzBW7ukQxQbn9N_6Q@mail.gmail.com>
2016-05-29 19:48 ` Julien Desfossez [this message]
[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='574B4791.905__18941.2097832703$1464551340$gmane$org@efficios.com' \
--to=jdesfossez@efficios.com \
--cc=lttng-dev@lists.lttng.org \
--cc=whalajam@gmail.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 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.