From: "Raphaël Beamonte" <raphael.beamonte@gmail.com>
To: linux-rt-users@vger.kernel.org, lttng-dev@lists.lttng.org
Cc: lwn@lwn.net
Subject: Non-Preempt Test v1.01
Date: Mon, 14 Oct 2013 15:05:14 -0400 [thread overview]
Message-ID: <525C406A.5050000@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]
Hi all !
I just released the Non-Preempt Test (npt) version 1.01 which is
available here: http://git.dorsal.polymtl.ca/?p=npt.git
The purpose of this tool is to simulate a small real-time system that
runs with a high priority without being stopped or preempted. To do so,
it first sets its environment (cpu affinity, RT scheduler, memory locked
into RAM with mlockall) and can optionally disable the local IRQs if
compiled with the right options (not defined by default).
The core of the application is a loop that calculates the time gap
between the start of two consecutive loops using the rdtsc asm
instruction, thus a similarity with the hwlat_detector kernel module for
kernel analysis. At the end of its execution, npt computes latencies
statistics for each loop and generates a histogram showing the different
latencies reached and the number of time it reached each one.
This tool can be used to analyse and identify overhead of different
realtime applications as we can compare the latencies in each loops and
thus identify the added latency from a "blank" run. It is released
LTTng-ready and can thus be easily traced. Next versions could include
other userspace tracers ability.
Feedback, collaborations and contributions are welcome!
Regards,
Raphaël Beamonte
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-10-14 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 19:05 Raphaël Beamonte [this message]
2013-10-14 22:04 ` Non-Preempt Test v1.01 Aaron Fabbri
2013-10-15 18:46 ` Raphaël Beamonte
2013-10-16 0:10 ` Aaron Fabbri
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=525C406A.5050000@gmail.com \
--to=raphael.beamonte@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
--cc=lwn@lwn.net \
/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.