From: Frank Rowand <frank.rowand@am.sony.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Bhavesh Davda <bhavesh@vmware.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH RT-TESTS] cyclictest: new command line switch for histogram overflow instance tracking
Date: Fri, 16 Nov 2012 18:01:17 -0800 [thread overview]
Message-ID: <50A6EFED.9000501@am.sony.com> (raw)
In-Reply-To: <50A584BE.2000107@am.sony.com>
On 11/15/12 16:11, Frank Rowand wrote:
< snip >
>> I would like to address all your suggestions. Which ones did I miss?
>
> | Add a line to the histogram overflow cycle report that merges all
> | threads into a single time line. This is controlled by the -H
> | option which already serves a similar purpose for histograms.
>
> The merged data line is an enhancement. If there is no strong request
> from anyone for the feature then no need to include. But it seems
> useful to me.
After adding in timestamps instead of cycle numbers, and playing
around with some actual data, I think that this feature is not
needed. It adds code complexity. The same result can be
achieved by sorting the data outside of cyclictest.
-Frank
prev parent reply other threads:[~2012-11-17 2:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <943398371.54180912.1352931103535.JavaMail.root@vmware.com>
2012-11-14 22:18 ` [PATCH RT-TESTS] cyclictest: new command line switch for histogram overflow instance tracking Bhavesh Davda
2012-11-14 23:42 ` Frank Rowand
2012-11-15 2:17 ` Bhavesh Davda
2012-11-16 0:11 ` Frank Rowand
2012-11-16 1:56 ` Bhavesh Davda
2012-11-16 2:04 ` Bhavesh Davda
2012-11-16 2:24 ` Frank Rowand
[not found] ` <50A6F713.7010806@am.sony.com>
2012-11-17 2:41 ` Frank Rowand
2012-11-26 21:14 ` Frank Rowand
2012-11-26 21:37 ` Bhavesh Davda
2012-11-29 17:28 ` Bhavesh Davda
2012-11-29 19:57 ` Frank Rowand
2012-12-12 1:45 ` Frank Rowand
2012-12-17 18:24 ` Bhavesh Davda
2012-12-17 21:34 ` Frank Rowand
2012-12-17 22:17 ` Bhavesh Davda
2012-12-17 23:30 ` Frank Rowand
2012-11-17 2:01 ` Frank Rowand [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=50A6EFED.9000501@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=bhavesh@vmware.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
/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).