All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frank.rowand@am.sony.com>
To: Bhavesh Davda <bhavesh@vmware.com>
Cc: John Kacur <jkacur@redhat.com>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH RT-TESTS] cyclictest: new command line switch for histogram overflow instance tracking
Date: Mon, 26 Nov 2012 13:14:20 -0800	[thread overview]
Message-ID: <50B3DBAC.90208@am.sony.com> (raw)
In-Reply-To: <50A6F963.9000207@am.sony.com>

On 11/16/12 18:41, Frank Rowand wrote:
> On 11/16/12 18:31, Frank Rowand wrote:
> 
> < snip >
>  
>> I graphed the results with the msec data and with the nanosecond
>> timestamps for an artificial test (two test runs for each case):
>>
>>   nanosecond:  junk7.gif    junk10.gif
>>   msec:        junk8_d.gif  junk9_d.gif
>>
>> The cyclictest latency disruptions seem more visible to me in the
>> nanosecond data graphs.  But that is just a first impression
>> without playing around with a lot of different data sets.
> 
> John, Bhavesh,
> 
> OK, so after all of that, I'm going on vacation for a week.
> I hope the rest of you are taking some time off too.

I'm back...  Bhavesh, have you had a chance to think about my last
several emails (my comments on your latest patch, my proposed patch,
and the email I'm responding to)?  Any comments?

> 
> My conclusion after my data creation and graphing exercise is that
> it might be good if people could play around with collecting and
> analyzing real histogram overflow data and see what data formats
> provide useful information.
> 
> I think we should not rush the patch into John's tree so that we
> aren't stuck with a format or type of data that is not optimal.
> 
> Bhavesh, if you created this feature based on a real world need
> (instead of just a brilliant mind exercise), it would be great
> if you could apply the latest iteration (or iterations in the
> near future) to your actual data collection and provide a real
> world example of how this feature makes cyclictest better.
> 
> Thanks,
> 
> Frank



  reply	other threads:[~2012-11-26 21:14 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 [this message]
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

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=50B3DBAC.90208@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.