public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Priority Inheritance Test (Real-Time Preemption)
Date: Tue, 30 Nov 2004 09:49:04 +0100	[thread overview]
Message-ID: <20041130084904.GA17799@elte.hu> (raw)
In-Reply-To: <Pine.OSF.4.05.10411291717120.14592-100000@da410.ifa.au.dk>


* Esben Nielsen <simlo@phys.au.dk> wrote:

> > and i'm regularly testing this property with 'hackbench 50', which
> > creates over a 1000 wildly scheduling non-RT tasks. Latency is not
> > affected by such workloads.
> >
>  
> Probably not. Even while doing that you most likely wont build up wait
> lists of more than 10, maybe 100 tasks? Doing full traversals with irq
> disabled probably wont be meassureable!(?) compared to much other
> stuff increasing responsible for the meassured latency.

there is no full list traversal of SCHED_NORMAL tasks, ever.

but the best way is to test this yourself, download Florian's rtc_wakeup
from:

  http://www.affenbande.org/~tapas/wiki/index.php?rtc_wakeup

and run it with the highest possible resolution, 8192 Hz:

  chrt -f 98 -p `pidof 'IRQ 8'`
  chrt -f 99 -p `pidof 'IRQ 0'`

  ./rtc_wakeup -f 8192 -t 100000

in this mode rtc_wakeup will report the worst irq-delivery latency it
measures. It will thus measure the combined effect of any type of
scheduling or irqs-off latency to RT-tasks.

then download hackbench from:

  http://developer.osdl.org/craiger/hackbench/

and try e.g.:

  ./hackbench 50

this will start 2x20x50 == 2000 SCHED_NORMAL threads, all performing a
nice pattern of scheduling simulating a busy chat server workload with
tons of messages going back and forth.

	Ingo

  reply	other threads:[~2004-11-30  8:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-21 20:29 Priority Inheritance Test (Real-Time Preemption) Esben Nielsen
2004-11-22  0:27 ` Ingo Molnar
2004-11-23 13:34   ` Ingo Molnar
2004-11-23 15:47     ` Esben Nielsen
2004-11-23 23:03     ` Esben Nielsen
2004-11-24  3:42       ` Ingo Molnar
2004-11-24  7:51         ` Ingo Molnar
2004-11-24  8:07       ` Ingo Molnar
2004-11-24  8:33         ` Esben Nielsen
2004-11-24  9:55           ` Ingo Molnar
2004-11-24 10:18       ` Ingo Molnar
2004-11-25 15:46         ` Esben Nielsen
2004-11-25 16:58           ` Ingo Molnar
2004-11-25 16:08             ` Esben Nielsen
2004-11-25 17:14               ` Ingo Molnar
2004-11-25 22:08             ` Esben Nielsen
2004-11-26  1:08               ` Ingo Molnar
2004-11-26  0:34                 ` Ingo Molnar
2004-11-26  0:37                   ` Ingo Molnar
2004-11-26  8:52                     ` Esben Nielsen
2004-11-26 16:26                 ` Esben Nielsen
2004-11-26 20:41                   ` Ingo Molnar
2004-11-26 21:05                     ` Ingo Molnar
2004-11-27 23:05                       ` Esben Nielsen
2004-11-28  8:42                         ` Ingo Molnar
2004-11-28 15:55                           ` Esben Nielsen
2004-11-29  9:59                             ` Ingo Molnar
2004-11-29 15:07                               ` Esben Nielsen
2004-11-29 15:56                                 ` Ingo Molnar
2004-11-29 15:57                                   ` Ingo Molnar
2004-11-29 16:50                                     ` Esben Nielsen
2004-11-30  8:49                                       ` Ingo Molnar [this message]
2004-11-22  9:23 ` Bill Huey
2004-11-22 12:37   ` Ingo Molnar
2004-11-22 21:25     ` Bill Huey
2004-11-22 14:16   ` john cooper
2004-11-22 15:24     ` Ingo Molnar
2004-11-23  1:19       ` john cooper
2004-11-23  8:13         ` Esben Nielsen
2004-11-23  9:21         ` Ingo Molnar
2004-11-22 21:30     ` Bill Huey
2004-11-23  1:34       ` john cooper
2004-11-22 16:12   ` Esben Nielsen

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=20041130084904.GA17799@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simlo@phys.au.dk \
    /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