From: Clark Williams <williams@redhat.com>
To: Carsten Emde <Carsten.Emde@osadl.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
RT-Users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH v2] rt-tests: Add option to force timeout to pmqtest
Date: Thu, 1 Apr 2010 12:41:40 -0500 [thread overview]
Message-ID: <20100401124140.49f4cfa1@torg> (raw)
In-Reply-To: <4BB209ED.80602@osadl.org>
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
On Tue, 30 Mar 2010 16:25:49 +0200
Carsten Emde <Carsten.Emde@osadl.org> wrote:
> On 03/29/2010 05:08 PM, Carsten Emde wrote:
> > This patch adds the program pmqtest to the rt-tests suite.
> > The test mechanism is the same as in ptsematest, svsematest
> > and friends, but it uses message queues to synchronize the
> > test threads. To test the - now hopefully fixed - kernel
> > problem that occurred when a timeout was specified, the
> > -T option is available.
> This patch adds the option -f to force a timeout condition of
> mq_timedreceive() to pmqtest - only meaningful along with -T.
>
> The call
> # pmqtest -Sp99 -i100 -d0 -T1 -f2
>
> will display
>
> #0: ID17791, P99, CPU0, I100; #1: ID17792, P99, CPU0, Cycles 8
> #2: ID17793, P99, CPU1, I100; #3: ID17794, P99, CPU1, Cycles 8
> #4: ID17795, P99, CPU2, I100; #5: ID17796, P99, CPU2, Cycles 8
> #6: ID17797, P99, CPU3, I100; #7: ID17798, P99, CPU3, Cycles 8
> #8: ID17799, P99, CPU4, I100; #9: ID17800, P99, CPU4, Cycles 8
> #10: ID17801, P99, CPU5, I100; #11: ID17802, P99, CPU5, Cycles 8
> #12: ID17803, P99, CPU6, I100; #13: ID17804, P99, CPU6, Cycles 8
> #14: ID17805, P99, CPU7, I100; #15: ID17806, P99, CPU7, Cycles 8
> #1 -> #0, Min 16, Cur 22, Avg 18, Max 24
> #3 -> #2, Min 13, Cur 14, Avg 14, Max 16
> #5 -> #4, Min 14, Cur 20, Avg 16, Max 20
> #7 -> #6, Min 13, Cur 14, Avg 14, Max 15
> #9 -> #8, Min 14, Cur 14, Avg 15, Max 19
> #11 -> #10, Min 13, Cur 13, Avg 16, Max 20
> #13 -> #12, Min 13, Cur 14, Avg 15, Max 19
> #15 -> #14, Min 13, Cur 14, Avg 15, Max 19
> etc.
>
> but the next cycle will only continue when the timeout of 2 seconds is
> elapsed.
>
> Signed-off-by: Carsten Emde <C.Emde@osadl.org>
Carsten,
Not ignoring you, just took a while for your task to get scheduled (I'm
an old uni-processor :)).
I'll pull these in and spin a new rt-tests tonight.
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-04-01 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 15:08 [PATCH] Add test of message queues to rt-tests Carsten Emde
2010-03-30 14:25 ` [PATCH v2] rt-tests: Add option to force timeout to pmqtest Carsten Emde
2010-04-01 0:22 ` [PATCH] rt-tests: Add timeout count to pmqtest's output Carsten Emde
2010-04-01 17:41 ` Clark Williams [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=20100401124140.49f4cfa1@torg \
--to=williams@redhat.com \
--cc=Carsten.Emde@osadl.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).