Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Babeltrace Buffer Warning
Date: Mon, 16 Apr 2012 09:52:06 -0400	[thread overview]
Message-ID: <20120416135206.GA26549@Krystal> (raw)
In-Reply-To: <524C960C5DFC794E82BE548D825F05CF29EE58@EU-MBX-04.mgc.mentorg.com>

* Oestman, Fredrik (Fredrik_Oestman at mentor.com) wrote:
> Mathieu Desnoyers wrote:
> > Salman Rafiq wrote:
> 
> > > My kernel traced files are very large in size, thus when I try to
> > > convert CTF->text using "babeltrace" and redirect output to a file
> > > using '>' operator, I get the following warnings: [...]
> 
> > lttng enable-channel --help
> 
> Just to clarify: These events were lost at trace time, not at convert time. Perhaps this isn't clear from the wording of the warning message.
> 

The warning message is:

"[warning] Tracer discarded 280625 events between [1334315833.578351009] and
[1334315833.578351380]. You should consider increasing the buffer size."

which states that the tracer did discard the events (not the converter).
But maybe I'm missing your point. What would you recommend to make this
message clearer ?

Thanks,

Mathieu


-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com



  reply	other threads:[~2012-04-16 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 12:58 Salman Rafiq
2012-04-13 13:01 ` Mathieu Desnoyers
2012-04-16  6:58   ` Oestman, Fredrik
2012-04-16 13:52     ` Mathieu Desnoyers [this message]
2012-04-16 14:11       ` Oestman, Fredrik
2012-04-16 14:32         ` Mathieu Desnoyers
2012-04-18  8:05           ` Salman Rafiq
2012-04-18 13:55             ` Mathieu Desnoyers
2012-04-18 15:25               ` Salman Rafiq
2012-04-18 20:31                 ` 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=20120416135206.GA26549@Krystal \
    --to=mathieu.desnoyers@efficios.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