linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Jain Priyanka-B32167 <B32167@freescale.com>
Cc: "williams@redhat.com" <williams@redhat.com>,
	Aggrwal Poonam-B10812 <B10812@freescale.com>,
	"jkacur@redhat.com" <jkacur@redhat.com>,
	"frank.rowand@am.sony.com" <frank.rowand@am.sony.com>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	Srivastava Rajan-B34330 <B34330@freescale.com>,
	"dvhart@linux.intel.com" <dvhart@linux.intel.com>
Subject: RE: [PATCH 3/4] Add cyclicload calibration & load generation feature
Date: Fri, 19 Oct 2012 11:39:38 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.02.1210191125480.3251@tycho> (raw)
In-Reply-To: <AC83832D6324604BB08FAE5A33553F190B175EC1@039-SN2MPN1-011.039d.mgd.msft.net>



On Fri, 19 Oct 2012, Jain Priyanka-B32167 wrote:

> Dear Clark,
> 
> Its along time that since I have send patches for cyclicload.
> I can see patch for cyclicload integrated into work branch on rt-test git tree.
> Did you have any feedback on its working.
> 
> Also I have made some improvements on it. Should I send the next version of the cyclicload patch or a new patch for the changes based on the 'work' branch code.
> 
> Regards
> Priyanka
> 
>
 
------------->o SNIP

Personally I think you should send the next version of the new patch, and 
not based on Clark's work branch. (a working branch is just that, a 
working place to store patches, no guarantees)

I think I should warn you that we have been discussing how difficult it is 
to make an artifical load. I worry that your program just adds a thread or 
threads spinning at another prio level, (which you can do already with 
cyclictest) but not adding any real load. I wouldn't like for you to do
 a lot of work only to have it ultimately rejected.

Why don't you submit the next version of your work, and then perhaps talk 
a little more about what you intend to do, and see what other people on 
the mailing list here think about that.

Thanks

John Kacur

  reply	other threads:[~2012-10-19 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30  9:56 [PATCH 0/4] Add cyclicload testtool support Priyanka Jain
2012-08-30  9:56 ` [PATCH 1/4] Add README for cyclicload test tool Priyanka Jain
2012-08-30  9:56 ` [PATCH 2/4] Duplicates cyclictest code as cyclicload Priyanka Jain
2012-08-30  9:56 ` [PATCH 3/4] Add cyclicload calibration & load generation feature Priyanka Jain
2012-10-19  4:32   ` Jain Priyanka-B32167
2012-10-19 15:39     ` John Kacur [this message]
2012-08-30  9:56 ` [PATCH 4/4] Add cyclicload manual page Priyanka Jain

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.02.1210191125480.3251@tycho \
    --to=jkacur@redhat.com \
    --cc=B10812@freescale.com \
    --cc=B32167@freescale.com \
    --cc=B34330@freescale.com \
    --cc=dvhart@linux.intel.com \
    --cc=frank.rowand@am.sony.com \
    --cc=linux-rt-users@vger.kernel.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).