From: John Kacur <jkacur@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, Sana Sharma <sansshar@redhat.com>
Subject: [ANNOUNCE] rteval-v3.13
Date: Wed, 26 Aug 2026 14:57:32 -0400 [thread overview]
Message-ID: <20260826185732.208384-1-jkacur@redhat.com> (raw)
I am happy to announce the release of rteval-3.13
rteval-3.13 introduces an MCP server for AI-assisted analysis of rteval
results, along with stress-ng usability improvements.
New Features:
* rteval-mcp - a new, optional MCP (Model Context Protocol) server for
analyzing rteval result files from an MCP-capable client. It provides
histogram extraction, percentile and per-CPU latency statistics,
result comparison, batch analysis, filtering, and log-file access.
* stress-ng stressor validation - invalid stressor names now produce a
clear error pointing at "stress-ng --stressors", and a helpful message
when stress-ng is not installed (Sana Sharma)
Improvements:
* stress-ng: apply taskset to keep stressors off the isolated CPUs
reserved for the measurement threads
* stress-ng: updated parameter names (Sana Sharma)
Documentation:
* Add README, demo, and enabling guides for the rteval-mcp server
To fetch
Clone
git://git.kernel.org/pub/scm/utils/rteval/rteval.git
Branch: main
Tag: v3.13
Tarballs available here:
https://kernel.org/pub/linux/utils/rteval
Older version tarballs are available here:
https://kernel.org/pub/linux/utils/rteval/older
To accommodate distributions that require this, I have linked the last
version v3.12 from the older directory to the current directory
Bug reports, patches, etc are always welcome.
--
2.55.0
reply other threads:[~2026-08-26 18:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260826185732.208384-1-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=sansshar@redhat.com \
--cc=williams@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;
as well as URLs for NNTP newsgroup(s).