From: John Kacur <jkacur@redhat.com>
To: Daniel Wagner <wagi@monom.org>
Cc: Clark Williams <williams@redhat.com>,
Daniel Wagner <dwagner@suse.de>,
linux-rt-users@vger.kernel.org
Subject: Re: [rt-tests 0/4] Streamlining code base?
Date: Tue, 8 Sep 2020 11:23:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.23.451.2009081104480.3804@fionn> (raw)
In-Reply-To: <20200907081313.vyw2ykaio6abfxfx@beryllium.lan>
On Mon, 7 Sep 2020, Daniel Wagner wrote:
> On Fri, Sep 04, 2020 at 11:40:06AM -0400, John Kacur wrote:
> > I'm not saying this is the only legitimate approach, but I would like to
> > keep the individual tools lightweight in rt-tests, so that you could run
> > them individually in the embedded space as well as on large machines.
>
> Sure, though I still think it would make sense to keep it flexible and
> have a compile switch if needed. I'd like to avoid additional steps
> between the measurement and interpretation. Any time we want to
> add/change a thing, we need to touch more places.
>
> Furthermore, if you look at my implementation for the JSON output of
> jitterdebugger is really small:
>
> https://github.com/igaw/jitterdebugger/blob/master/jitterdebugger.c#L158
>
> Adding a XML version for this should be in the same size.
>
> If you insist on a single format (XML) that's also okay for me. Python
> ships all the necessary libraries these days. Though the JSON format is
> simpler to transform into native data types such as dictionaries and
> lists, IMO.
If you just read a text stream like rteval does, and store in a native
data type, then it is trivial to output any data format.
However, your implementation for your jitterdebugger is truly small,
I don't want to stomp on your creativity, so spin off a git branch and go
to it. I can be persuaded.
John
prev parent reply other threads:[~2020-09-08 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 8:27 [rt-tests 0/4] Streamlining code base? Daniel Wagner
2020-09-02 8:27 ` [rt-tests 1/4] cyclicdeadline: Streamline usage output and man page Daniel Wagner
2020-09-02 8:27 ` [rt-tests 2/4] deadline_test: " Daniel Wagner
2020-09-02 8:27 ` [rt-tests 3/4] oslat: " Daniel Wagner
2020-09-02 8:27 ` [rt-tests 4/4] oslat: Use string parser utilies Daniel Wagner
2020-09-04 1:39 ` [rt-tests 0/4] Streamlining code base? Clark Williams
2020-09-04 6:31 ` Daniel Wagner
2020-09-04 15:40 ` John Kacur
2020-09-07 8:13 ` Daniel Wagner
2020-09-08 15:23 ` John Kacur [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=alpine.LFD.2.23.451.2009081104480.3804@fionn \
--to=jkacur@redhat.com \
--cc=dwagner@suse.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=wagi@monom.org \
--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).