Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: salman.rafiq@esk.fraunhofer.de (Salman Rafiq)
Subject: [lttng-dev] Babeltrace Buffer Warning
Date: Wed, 18 Apr 2012 10:05:14 +0200	[thread overview]
Message-ID: <E537659DE2B2C54EBD9FC9180F0598803902C370E6@zulu.esk.fraunhofer.de> (raw)
In-Reply-To: <20120416143231.GA27877@Krystal>

Hello All,

Increasing the number of buffers and buffer size did helped indeed. Thanks to both for the advice.

Another question is, what is the maximum --subbuf-size & --num-subbuf one can go? I guess it should depend upon your memory size?

I am asking this because I had trouble last time, where my system crashed with some "general protection fault" while I had --subbuf-size of 2^29 . Attached are the syslog messages.


Regards,
S.

--
Salman Rafiq
Industrial Communication
Fraunhofer-Einrichtung f?r Systeme der Kommunikationstechnik ESK

Hansastra?e 32 | 80686 M?nchen
Telefon, Fax:  +49 89 547088-356 | +49 89 547088-66-356
E-Mail:   salman.rafiq at esk.fraunhofer.de

Internet:
http://www.esk.fraunhofer.de
http://www.facebook.com/FraunhoferESK
http://www.twitter.com/FraunhoferESK


-----Urspr?ngliche Nachricht-----
Von: Mathieu Desnoyers [mailto:mathieu.desnoyers at efficios.com]
Gesendet: Monday, April 16, 2012 4:33 PM
An: Oestman, Fredrik
Cc: lttng-dev at lists.lttng.org; Salman Rafiq
Betreff: Re: [lttng-dev] Babeltrace Buffer Warning

* Oestman, Fredrik (Fredrik_Oestman at mentor.com) wrote:
> Mathieu Desnoyers wrote:
> > 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 ?
>
> I actually had no recommendation or suggestion in mind. To me the message is clear. I just got the impression that the OP may have been confused in this respect for some reason.
>
> But since you ask, what about something along the lines of:
>
> "[warning] The tracer discarded 280625 events between
> [1334315833.578351009] and [1334315833.578351380]. You should consider
> making a new trace with larger buffers or with fewer event types enabled."

Good idea. Fixed in commit:

commit a0b34fbba498a8a447357adf5920ac2c8a22f026
Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Date:   Mon Apr 16 10:33:55 2012 -0400

    Clarify warning message for events discarded

    Reported-by: Fredrik Oestman <Fredrik_Oestman at mentor.com>
    Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>

Thanks!

Mathieu


>
>
> Cheers,
>
> Fredrik ?stman
>

--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant EfficiOS Inc.
http://www.efficios.com
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: command_line.txt
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20120418/9ebf02ae/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: syslogd.txt
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20120418/9ebf02ae/attachment-0001.txt>


  reply	other threads:[~2012-04-18  8:05 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
2012-04-16 14:11       ` Oestman, Fredrik
2012-04-16 14:32         ` Mathieu Desnoyers
2012-04-18  8:05           ` Salman Rafiq [this message]
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=E537659DE2B2C54EBD9FC9180F0598803902C370E6@zulu.esk.fraunhofer.de \
    --to=salman.rafiq@esk.fraunhofer.de \
    /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