All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frank.rowand@am.sony.com>
To: John Kacur <jkacur@redhat.com>, Bhavesh Davda <bhavesh@vmware.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH RT-TESTS] cyclictest: histogram overflow instance tracking
Date: Tue, 13 Nov 2012 16:02:54 -0800	[thread overview]
Message-ID: <50A2DFAE.7010306@am.sony.com> (raw)
In-Reply-To: <880517104.255767.1352850809690.JavaMail.root@redhat.com>

On 11/13/12 15:53, John Kacur wrote:
> 
> 
> ----- Original Message -----
>> Hello Frank,
>>
>> I apologize I didn't have a chance to review your proposed
>> modifications to my patch.
>>
>> I had looked at your proposal to introduce a '-g' option (for lack of
>> a better letter) instead of piggy-backing on the '-h' option, and I
>> completely agree with that approach.
>>
>> It would be very handy to specify, for example, '-h 50 -g 1000' to
>> capture and print the 1000 outliers beyond 50 us to get a good sense
>> of any patterns hidden in the outliers.
>>
>> If John has already accepted my proposed patches, do you want to
>> propose your changes on top of that as a separate patch now?

Bhavesh,

I would agree with John's suggestions (the following paragraph).  I did not
want to hijack your feature, but instead just help make it better, so I was
phrasing my stuff as suggestions, not as "you must do this" type of
additions.  So I would prefer you still own the feature.  If you propose
a further patch based on my suggestions, I will review and test it.

> 
> Please pull the git tree, have a look at what I put in, and then think about
> Frank's suggestions. Make sure you are "proactive" - (oh God, thinking about 
> a Simpson's episode now), and see what you can do with it, instead of just
> waiting for Frank to tell you his opinions.
> 
> Thanks!
> 
>>
>> Thanks for your review, and your excellent suggestion to make this
>> feature even more useful.
>>
>> --
>> Bhavesh Davda

< snip >


  reply	other threads:[~2012-11-14  0:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 17:02 [PATCH RT-TESTS] cyclictest: histogram overflow instance tracking Bhavesh Davda
2012-10-23  1:16 ` Frank Rowand
2012-10-23  1:41   ` Frank Rowand
2012-10-23 18:59     ` Bhavesh Davda
2012-10-23 19:25       ` John Kacur
2012-10-23 19:55         ` Frank Rowand
2012-10-23 19:59           ` Sven-Thorsten Dietrich
2012-10-25 21:36 ` Frank Rowand
2012-10-25 22:05   ` Frank Rowand
2012-11-13 23:41     ` Frank Rowand
2012-11-13 23:41   ` Frank Rowand
2012-11-13 23:48     ` Bhavesh Davda
2012-11-13 23:53       ` John Kacur
2012-11-14  0:02         ` Frank Rowand [this message]
2012-11-14  0:03         ` Bhavesh Davda
2012-11-14  0:04           ` Bhavesh Davda
2012-11-14  0:09             ` John Kacur
2012-11-14  0:17               ` Bhavesh Davda
2012-11-14  0:19                 ` 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=50A2DFAE.7010306@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.