From: Dragan Noveski <perodog@gmx.net>
To: linux-rt-users@vger.kernel.org
Subject: Re: 2.6.23.1-rt9 (and others)
Date: Wed, 07 Nov 2007 21:04:10 +0000 [thread overview]
Message-ID: <4732284A.6070501@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0711071454450.1040@gandalf.stny.rr.com>
Steven Rostedt wrote:
> On Wed, 7 Nov 2007, Dragan Noveski wrote:
>
>
>> Steven Rostedt wrote:
>>
>>> Currently, what we do to test RT latencies is to run Thomas Gleixner's
>>> cyclictest
>>> (http://git.kernel.org/?p=linux/kernel/git/tglx/rt-tests.git;a=summary)
>>> as well as hackbench, to see what the maximum latencies we get are.
>>>
>>>
>> hallo, can please someone suggest for how long time you are running
>> cyclictest?
>> if i run it for about 3 min. i get a feeling that the values will not
>> change anymore, so is there any recommended time for how long to run it?
>>
>
> Actually, you want to run it for a long time, and under very heavy load.
> I'm currently running it while doing a "make -j128" on a kernel tree. This
> takes several hours to complete the make. So far with -rt11 I have a max
> latency with one RT thread at the prio of 98 68us.
>
> When you do run cyclic test, make sure you run it at a higher priority
> than the irq threads. And also use the -n option since the default is to
> test signals, and that part of the test isn't working so well.
>
> Here's what I'm running right now:
>
> ./cyclictest -n -p98 -t1 -i250
>
ok, i was trying like './cyclictest -n -t3 -p99' but i ll have a look
into -t and -i options more deeper now. but i was running it always for
about 3-4 minutes....
> While doing that "make -j120"
>
>
>> another thing i do not know is, if i run cyclictest for lets say 3
>> minutes, than stop ('ctrl+c') and than start again, i get often
>> different values. so is it recommended to run it more times and than to
>> pick up the best/worst cases.
>>
>> i have done some tests already with rt7,8 and 10 but i am not sure if
>> the tests make any sense - thats why i would really appreciate some
>> answers on the both questions.
>>
>>
>
> Actually I didn't want to discourage you. For UP, -rt7,8 and 10 really
> should be exactly the same (with some noise factures apart). The changes
> that were made supposable only affect SMP boxes. But, I'm glad you are
> doing the tests, since we also would like to know if anything creeped into
> te UP side, and has caused any regressions.
>
i was expecting this part about 'smp boxes' but anyway, as now i know
how to run cyclictest, i will be able to do again and again as the
development goes on.
> Thanks, for taking the time to test this.
>
> -- Steve
>
>
i thank you to for this very informative response!
cheers,
doc
prev parent reply other threads:[~2007-11-07 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 5:39 2.6.23.1-rt9 (and others) Steven Rostedt
2007-11-07 14:17 ` Dragan Noveski
2007-11-07 13:40 ` Gregory Haskins
2007-11-07 15:10 ` Dragan Noveski
2007-11-07 16:33 ` Steven Rostedt
2007-11-07 20:40 ` Dragan Noveski
2007-11-07 18:10 ` Dragan Noveski
2007-11-07 18:11 ` Dragan Noveski
2007-11-07 14:20 ` [PATCH] RT: fix uniprocessor build issue with new scheduler enhancements Gregory Haskins
2007-11-07 15:41 ` 2.6.23.1-rt9 (and others) Steven Rostedt
2007-11-07 22:51 ` Gregory Haskins
2007-11-07 20:41 ` Dragan Noveski
2007-11-07 19:59 ` Steven Rostedt
2007-11-07 21:04 ` Dragan Noveski [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=4732284A.6070501@gmx.net \
--to=perodog@gmx.net \
--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.