From: Peter Xu <peterx@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
peterx@redhat.com, Andrew Theurer <atheurer@redhat.com>,
John Kacur <jkacur@redhat.com>,
Clark Williams <williams@redhat.com>
Subject: [PATCH 0/2] rt-tests: Port oslat in
Date: Mon, 17 Aug 2020 17:55:03 -0400 [thread overview]
Message-ID: <20200817215505.227046-1-peterx@redhat.com> (raw)
This series ported the oslat program [1] into rt-tests repo.
Oslat is an userspace polling mode test to mimic DPDK apps. It can be used to
identify RT issues besides the general timer based tests like cyclictest.
The 1st patch is a cleanup for cyclictest to move some trace helpers into
rt-utils.[ch] files so that oslat can use too. The 2nd patch is the port.
For more information on oslat, please either refer to [1] below, or please read
the manual file in the 2nd patch.
Please review, thanks.
[1] https://github.com/xzpeter/oslat
Peter Xu (2):
rt-tests: cyclictest: Move ftrace helpers into rt-utils.[ch]
rt-tests: oslat: Init commit
.gitignore | 1 +
Makefile | 10 +-
src/cyclictest/cyclictest.c | 90 +---
src/include/rt-utils.h | 3 +
src/lib/rt-utils.c | 82 ++++
src/oslat/oslat.8 | 66 +++
src/oslat/oslat.c | 896 ++++++++++++++++++++++++++++++++++++
7 files changed, 1057 insertions(+), 91 deletions(-)
create mode 100644 src/oslat/oslat.8
create mode 100644 src/oslat/oslat.c
--
2.26.2
next reply other threads:[~2020-08-17 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 21:55 Peter Xu [this message]
2020-08-17 21:55 ` [PATCH 1/2] rt-tests: cyclictest: Move ftrace helpers into rt-utils.[ch] Peter Xu
2020-08-18 20:51 ` John Kacur
2020-08-17 21:55 ` [PATCH 2/2] rt-tests: oslat: Init commit Peter Xu
2020-08-18 20:54 ` John Kacur
2020-08-19 18:58 ` John Kacur
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=20200817215505.227046-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=atheurer@redhat.com \
--cc=jkacur@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mtosatti@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