All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Jaswinder Singh <jaswinderlinuxrt@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Cyclictest expected results
Date: Sun, 30 Sep 2007 20:32:53 +0200	[thread overview]
Message-ID: <20070930183253.GW23573@pengutronix.de> (raw)
In-Reply-To: <1985e0f60709300837l1b16deedgb15575bc73a729ad@mail.gmail.com>

On Sun, Sep 30, 2007 at 09:07:19PM +0530, Jaswinder Singh wrote:
> Here are my results on Intel Pentium 4 :
>
> Command line :  ./cyclictest -t 1 -p 80 -i 10000 -l 10000 -q

Can you post the output of /proc/timer_list?

> 2.6.23-rc8-rt1 :
> WARNING: High resolution timers not available
> T: 0 ( 2003) P:80 I:10000 C:  10000 Min:   1500 Act: 6129 Avg: 4502 Max:    7832

That one should give you sane results.

> From where I can get Linux-2.6.16-hrt5 and Linux-2.6.16-rt12 patches.

I don't think it makes much sense to play with such an old kernel any more.

> CONFIG_HIGH_RES_TIMERS=y are defined in .config then why I am getting
> "WARNING: High resolution timers not available".
>
> Why my results are not so impressive in realtime even though I defined:
> CONFIG_PREEMPT_RT=y
> CONFIG_PREEMPT=y
> CONFIG_PREEMPT_SOFTIRQS=y
> CONFIG_PREEMPT_HARDIRQS=y
> CONFIG_PREEMPT_BKL=y

Doesn't look too bad. Are you sure you actually _bootet_ that kernel? :)

> Min, Avg and Max are showing cyclic latencies. Ideally It should be
> ZERO. Am I right ?

You won't get zero. On x86 these latencies should be well below 100 us
maximum time, with an average in the lower 10 us range.

Robert
-- 
Pengutronix - Linux Solutions for Science and Industry
Entwicklungszentrum Nord     http://www.pengutronix.de

  reply	other threads:[~2007-09-30 18:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 15:37 Cyclictest expected results Jaswinder Singh
2007-09-30 18:32 ` Robert Schwebel [this message]
2007-09-30 22:00   ` Thomas Gleixner
2007-09-30 22:26     ` Robert Schwebel
2007-09-30 23:14       ` Thomas Gleixner
2007-10-01  3:30     ` Jaswinder Singh
2007-10-02  6:54       ` Robert Schwebel
2007-10-07 12:50         ` Jaswinder Singh
2007-10-08 14:06           ` Robert Schwebel
2007-10-08 14:46             ` Jaswinder Singh
2007-10-08 15:09             ` Jaswinder Singh
2007-10-08 15:42               ` Thomas Gleixner
2007-10-08 14:55           ` Theodore Tso
2007-10-08 14:55             ` Luis Claudio R. Goncalves

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=20070930183253.GW23573@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=jaswinderlinuxrt@gmail.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.