All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: Tobias Knutsson <tobias.knutsson@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Cyclictest usage
Date: Mon, 11 Aug 2008 09:55:55 -0400	[thread overview]
Message-ID: <48A044EB.7010508@novell.com> (raw)
In-Reply-To: <ccb913ac0808110638v79283450j8d4953bc0820e747@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]

Hi Tobias,

  Some more questions (inline)

Tobias Knutsson wrote:
> 2.6.25.8-rt7 and 2.6.25.8
>
> On Mon, Aug 11, 2008 at 14:48, Gregory Haskins <ghaskins@novell.com> wrote:
>   
>> Tobias Knutsson wrote:
>>     
>>> Hello,
>>>
>>> I'm trying to do some initial benchmarking on a rt-kernel versus a
>>> vanilla kernel. On the rt the results are stable in between test runs
>>> using the following command:
>>>
>>> cyclictest -t 1 -p 80 -c 1 -n -i 10000 -l 10000
>>>       

What architecture is this?  And what do you see for ave/max in the 
cyclictest output on -rt (so we have a reference)


>>> However, using the same command while running the vanilla kernel, I
>>> get very varying results. And I would completely understand if it was
>>> due to increased jitter. The thing is, the jitter is very low (0%
>>> load) but the average times varies from 600 us to 6500 us depending on
>>> when the test is initiated.
>>>       

What are you considering "jitter" when you say it is very low?  Are the 
600-6500us values truly from the "ave" output of cyclictest, or are 
these an average of the "max" output?


>>> I imagine this might have something to do with not having high res
>>> timers in the vanilla kernel.

I will defer to Thomas, but my understanding is that 2.6.25 vanilla 
should have HRT as an option (though I am not sure if you enabled it or 
not).

>>>  If that is what's causing my problems.
>>>       

Cyclictest will report that it cannot access the HRT when it cannot find 
it (at least it does on my system, but I might have an older version 
running).  Do you see any such warnings?

>>> What is the best way of comparing the two kernels?
>>>       

This is a pretty good way, as long as you have HRT in the vanilla 
kernel.  Assuming for a second that you do, your results are showing you 
what I would expect to see for vanilla (600-6500us spikes).

HTH

-Greg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  parent reply	other threads:[~2008-08-11 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11  9:00 Cyclictest usage Tobias Knutsson
2008-08-11 12:48 ` Gregory Haskins
     [not found]   ` <ccb913ac0808110638v79283450j8d4953bc0820e747@mail.gmail.com>
2008-08-11 13:55     ` Gregory Haskins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-26 16:25 cyclictest usage Clark Williams
2017-06-02  9:59 ` Sebastian Andrzej Siewior
2017-06-02 14:26   ` Clark Williams
2017-06-02 16:54     ` Austin Schuh
2017-06-08  8:46       ` Sebastian Andrzej Siewior
2017-06-08  8:40     ` Sebastian Andrzej Siewior

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=48A044EB.7010508@novell.com \
    --to=ghaskins@novell.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tobias.knutsson@gmail.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 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.