From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTT : cpu : 32043 events lost in cpu channel (cpu 1).
Date: Fri, 5 Dec 2008 06:16:51 -0500 [thread overview]
Message-ID: <20081205111651.GA23312@Krystal> (raw)
In-Reply-To: <8d94e9280812050249g62c6953wc5db71146608e6b2@mail.gmail.com>
* Gian Lorenzo Meocci (glmeocci at gmail.com) wrote:
> Hi all,
>
> I am trying to trace x264 code with a SCHED_RR policy for all threads.
> When I use this policy or SCHED_FIFO policy I always obtain this
> error:
>
> LTT : cpu : 32043 events lost in cpu channel (cpu 1).
>
> I am using:
> Linux 2.6.27.4-profiled #2 SMP Fri Nov 7 14:17:36 CET 2008 i686 GNU/Linux
> Linux Trace Toolkit Trace Daemon 0.57-28102008
> Linux Trace Toolkit Visualizer 0.11.5-06112008
>
Try
- Increasing the buffer size (see high event rate buffer size in lttctl
--help) or the number of subbuffers. Note that those are both rounded
to the next power of two.
- Running in flight recorder mode. You would then have only the last X
events from the trace, but you won't be limited by your disk output.
- Having a faster disk output.
- Looking at the most frequent events in the trace and disabling this
instrumentation. using lttv -m textDump --noevent path_to_trace
should help finding the most frequent event.
Mathieu
>
> Thanks a lot,
>
> --
> Ing. Gian Lorenzo Meocci
> http://www.meocci.it
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2008-12-05 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 10:49 Gian Lorenzo Meocci
2008-12-05 11:16 ` Mathieu Desnoyers [this message]
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=20081205111651.GA23312@Krystal \
--to=compudj@krystal.dyndns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox