From: Gabriele Monaco <gmonaco@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>, Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
John Kacur <jkacur@redhat.com>,
Luis Goncalves <lgoncalv@redhat.com>
Subject: Re: [PATCH 4/4] rtla: Report missed event count
Date: Fri, 24 Jan 2025 10:24:29 +0100 [thread overview]
Message-ID: <3568976320e31a90e36f7d2a17ec7d42e1f2f34a.camel@redhat.com> (raw)
In-Reply-To: <20250123142339.990300-5-tglozar@redhat.com>
On Thu, 2025-01-23 at 15:23 +0100, Tomas Glozar wrote:
> Print how many events were missed by trace buffer overflow in the
> main
> instance at the end of the run (for hist) or during the run (for
> top).
>
> Signed-off-by: Tomas Glozar <tglozar@redhat.com>
> ---
The patchset seems to work as expected, I get the number of dropped
events and the percentage, of course if I let it run too long, I get
unknown number.
Tested on a 128 cores arm64 box with -p100, known to miss events:
run for 5s
4611870 (24.12%) events missed, results might not be accurate
run for 1m
104653605 (45.44%) events missed, results might not be accurate
run for 5m
539717695 (46.85%) events missed, results might not be accurate
run for 10m
1098569155 (47.68%) events missed, results might not be accurate
run for 1h
6749574550 (48.83%) events missed, results might not be accurate
Tested-by: Gabriele Monaco <gmonaco@redhat.com>
prev parent reply other threads:[~2025-01-24 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 14:23 [PATCH 0/4] rtla: Collect and print number of missed events Tomas Glozar
2025-01-23 14:23 ` [PATCH 1/4] rtla: Count missed trace events Tomas Glozar
2025-01-23 14:23 ` [PATCH 2/4] rtla: Count all processed events Tomas Glozar
2025-01-23 14:23 ` [PATCH 3/4] rtla: Add function to report missed events Tomas Glozar
2025-01-23 14:23 ` [PATCH 4/4] rtla: Report missed event count Tomas Glozar
2025-01-24 9:24 ` Gabriele Monaco [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=3568976320e31a90e36f7d2a17ec7d42e1f2f34a.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=jkacur@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.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
all inboxes | Powered by JetHome®