From: Lee Revell <rlrevell@joe-job.com>
To: markh@compro.net
Cc: linux-kerneL@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: RT exec for exercising RT kernel capabilities
Date: Fri, 14 Jul 2006 18:34:15 -0400 [thread overview]
Message-ID: <1152916456.3119.92.camel@mindpipe> (raw)
In-Reply-To: <448876B9.9060906@compro.net>
On Thu, 2006-06-08 at 15:12 -0400, Mark Hounschell wrote:
> ftp://ftp.compro.net/public/rt-exec/
The high res timers do not seem to be working. Using 2.6.17-rt3 and
glibc 2.3.6, I get the exact same (bad) results whether
CONFIG_HIGH_RES_TIMERS is enabled or not.
CONFIG_HIGH_RES_TIMERS=y, CONFIG_HIGH_RES_RESOLUTION=1000:
# Run 00:40:12:784 Posix-hrt 14:27:38 Work:200 CPU:14 Avg:14 Max:23 Pg:0
# DataPool:SHM Exec Heart Beat Rate:1000Hz Exec Revision:1.0.3-1
###############################################################################
# Task Sched Cpu Intr Late -Interrupt Latencies (usec)-
# Taskname Type Pr P Mask Cnt Cnt Spare Current Best Worst Determ
# exec hrt 5 F 2 2412784 0 871 2 1 18 17
# task1 dth 29 F 2 603196 0 3993 19 17 70 53
# task2 dth 28 F 2 603196 1 3993 19 17 128 111
# task3 sth 25 F 2 1206392 0 1993 18 14 40 26
# task4 sth 24 F 2 1206392 0 1993 18 13 37 24
# task5 sem 23 F 2 2412784 0 993 4 3 28 25
# task6 sem 22 F 2 1206392 0 1993 4 3 10 7
# task7 sig 19 F 2 1206392 0 1993 7 7 17 10
# task8 sig 18 F 2 1206392 0 1993 8 6 18 12
# task9 hrt 17 R 2 1017659 0 1993 763 712 2185 1473
# task10 hrt 17 R 2 1017798 0 1993 771 717 13879 13162
# task11 hrn 14 R 2 1586789 0 993 1060 690 15817 15127
# task12 hrn 14 R 2 1586620 0 993 1024 689 15743 15054
# task13 hru 11 R 2 1557359 0 993 1053 689 2972 2283
# task14 hru 11 R 2 1561189 0 993 1018 690 3010 2320
# task15 bth 7 R 2 2412784 0 994 29 13 55 42
# task16 bth 7 R 2 2412784 0 993 14 13 56 43
CONFIG_HIGH_RES_TIMERS=n:
# Run 00:03:59:384 Posix-hrt 18:24:45 Work:200 CPU:14 Avg:14 Max:19 Pg:0
# DataPool:SHM Exec Heart Beat Rate:1000Hz Exec Revision:1.0.3-1
###############################################################################
# Task Sched Cpu Intr Late -Interrupt Latencies (usec)-
# Taskname Type Pr P Mask Cnt Cnt Spare Current Best Worst Determ
# exec hrt 5 F 2 239384 0 870 1 1 13 12
# task1 dth 29 F 2 59847 0 3993 19 17 39 22
# task2 dth 28 F 2 59846 0 3993 19 17 39 22
# task3 sth 25 F 2 119693 0 1993 18 17 37 20
# task4 sth 24 F 2 119692 0 1993 19 14 41 27
# task5 sem 23 F 2 239385 0 993 5 4 26 22
# task6 sem 22 F 2 119693 0 1993 5 4 9 5
# task7 sig 19 F 2 119693 0 1993 8 7 15 8
# task8 sig 18 F 2 119692 0 1993 8 6 15 9
# task9 hrt 17 R 2 104060 0 1992 1108 724 11439 10715
# task10 hrt 17 R 2 104057 0 1993 1102 726 12923 12197
# task11 hrn 14 R 2 161028 0 994 1056 705 13001 12296
# task12 hrn 14 R 2 160951 0 993 1019 704 12456 11752
# task13 hru 11 R 2 158334 0 993 1054 744 3109 2365
# task14 hru 11 R 2 158729 0 993 1020 709 3066 2357
# task15 bth 7 R 2 239385 0 993 29 13 54 41
# task16 bth 7 R 2 239385 0 993 15 13 55 42
Any idea what could be wrong?
Lee
next prev parent reply other threads:[~2006-07-14 22:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 19:12 RT exec for exercising RT kernel capabilities Mark Hounschell
2006-06-08 19:46 ` Thomas Gleixner
2006-06-08 20:50 ` Mark Hounschell
2006-06-09 11:53 ` Mark Hounschell
2006-06-09 20:04 ` Mark Hounschell
2006-06-09 20:11 ` Thomas Gleixner
2006-06-09 9:15 ` Serge Noiraud
2006-06-09 17:20 ` Lee Revell
2006-06-10 9:50 ` Antonio
2006-06-13 14:13 ` Serge Noiraud
2006-06-13 14:34 ` Mark Hounschell
2006-06-13 14:48 ` Serge Noiraud
2006-06-13 14:53 ` Mark Hounschell
2006-06-13 16:24 ` Mark Hounschell
2006-07-14 22:34 ` Lee Revell [this message]
2006-07-15 2:04 ` Thomas Gleixner
2006-07-15 2:10 ` Lee Revell
2006-07-17 14:20 ` Mark Hounschell
2006-07-21 18:17 ` Lee Revell
2006-10-02 22:27 ` Lee Revell
2006-10-02 22:39 ` Thomas Gleixner
2006-10-03 11:14 ` Mark Hounschell
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=1152916456.3119.92.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kerneL@vger.kernel.org \
--cc=markh@compro.net \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 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.