From: Punit Agrawal <punitagrawal@gmail.com>
To: jkacur@redhat.com
Cc: Punit Agrawal <punitagrawal@gmail.com>,
linux-rt-users@vger.kernel.org, punit1.agrawal@toshiba.co.jp,
Venkata.Pyla@toshiba-tsip.com, dinesh.kumar@toshiba-tsip.com
Subject: [PATCH 0/3] rteval: Fix issues with cyclictest.py module
Date: Thu, 2 Sep 2021 18:24:49 +0900 [thread overview]
Message-ID: <20210902092452.726905-1-punitagrawal@gmail.com> (raw)
Hi,
A few areas of improvements to the cyclictest module were noted while
using rteval to evaluate latencies. The following small set of patches
address these.
The first patch persists the output of "cyclictest" - which is helpful
in getting more information than what is reported by rteval. It can
also help sanity check rteval output when needed.
The second patch uses the max latencies reported by cyclictest vs only
relying on the histogram latencies.
The third patch fixes the ordering of reported latencies.
All feedback welcome.
Thanks,
Punit
Punit Agrawal (3):
rteval: cyclictest.py Enable logging cyclictest output
rteval: cyclictest.py Parse max latencies from cyclictest ouput
rteval: misc.py: Sort the list of cpus returned by online_cpus()
rteval/misc.py | 1 +
rteval/modules/measurement/cyclictest.py | 36 +++++++++++++++++++-----
2 files changed, 30 insertions(+), 7 deletions(-)
--
2.32.0
next reply other threads:[~2021-09-02 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 9:24 Punit Agrawal [this message]
2021-09-02 9:24 ` [PATCH 1/3] rteval: cyclictest.py Enable logging cyclictest output Punit Agrawal
2021-09-12 15:03 ` John Kacur
2021-09-02 9:24 ` [PATCH 2/3] rteval: cyclictest.py Parse max latencies from cyclictest ouput Punit Agrawal
2021-09-02 9:24 ` [PATCH 3/3] rteval: misc.py: Sort the list of cpus returned by online_cpus() Punit Agrawal
2021-09-12 15:39 ` John Kacur
2021-09-08 14:19 ` [PATCH 0/3] rteval: Fix issues with cyclictest.py module Punit Agrawal
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=20210902092452.726905-1-punitagrawal@gmail.com \
--to=punitagrawal@gmail.com \
--cc=Venkata.Pyla@toshiba-tsip.com \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=punit1.agrawal@toshiba.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).