All of lore.kernel.org
 help / color / mirror / Atom feed
From: edward.robbins@domain.hid
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Very high latencies under stress testing
Date: Sat, 23 Oct 2010 12:08:26 +0100 (BST)	[thread overview]
Message-ID: <1287832106.517512323@domain.hid> (raw)
In-Reply-To: <4CBDF92F.20403@domain.hid>

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

Thanks, this script sounds like exactly what I need. I downloaded the latest snapshot of mkrootfs from git, but I don't want to install that on my rootfs. I'd just download the script alone, but looking at it I see it would want to run a script in /ltp as well, so I guess I need ltp too. Can you tell me an easier way to set up dohell that might save me sifting through the whole of ltp and mkrootfs to figure it out?

Thanks again,

Edward

On Tuesday, 19 October, 2010 9:01pm, "Gilles Chanteperdrix" <gilles.chanteperdrix@domain.hid> said:

> edward.robbins@domain.hid.uk wrote:
> > Having disabled MTRR (and leaving in Phillipes patch) I am not
> > getting unreasonable latencies unless I enable graphics acceleration.
> > Can I be sure this has solved the issue?
> 
> Yes, run a long stress test while running latency. The stress test
> should stress anything (drivers, kernel services) you plan to use in the
> final system.
> 
> The way we do this when validating Xenomai is by running the "dohell"
> scripts, which relies on LTP to stress many kernel services.
> http://git.xenomai.org/?p=mkrootfs.git;a=blob;f=tests/dohell;h=327a9f20755e23547f960e4c316141652f839bbf;hb=master
> 
> --
>                                                                 Gilles.
> 

[-- Attachment #2: Type: text/html, Size: 1438 bytes --]

  reply	other threads:[~2010-10-23 11:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 14:17 [Xenomai-help] Very high latencies under stress testing edward.robbins
2010-08-13 14:35 ` Gilles Chanteperdrix
2010-08-16 12:13   ` edward.robbins
2010-08-16 12:32     ` Gilles Chanteperdrix
2010-09-03 16:30       ` edward.robbins
2010-09-04  8:51         ` Philippe Gerum
2010-10-15  9:21           ` edward.robbins
2010-10-15 11:54             ` edward.robbins
2010-10-15 13:51               ` Gilles Chanteperdrix
2010-10-15 14:13                 ` edward.robbins
2010-10-15 14:25                   ` Gilles Chanteperdrix
2010-10-15 14:33                   ` Philippe Gerum
2010-10-19 13:52                 ` edward.robbins
2010-10-19 20:01                   ` Gilles Chanteperdrix
2010-10-23 11:08                     ` edward.robbins [this message]
2010-10-23 11:13                       ` Gilles Chanteperdrix
2010-10-23 11:22                         ` edward.robbins
2010-10-23 11:36                           ` Gilles Chanteperdrix
2010-10-23 13:45                             ` edward.robbins
2010-10-23 13:51                               ` Gilles Chanteperdrix
2010-10-23 13:56                                 ` edward.robbins
2010-10-23 13:58                                   ` Gilles Chanteperdrix
2010-10-23 14:32                                     ` edward.robbins
2010-10-23 14:37                                       ` Gilles Chanteperdrix
2010-10-23 14:48                                         ` edward.robbins
2010-10-23 15:16                                       ` edward.robbins
2010-10-23 14:10                                   ` Gilles Chanteperdrix
2010-08-13 14:40 ` Philippe Gerum
2010-08-13 16:15   ` Philippe Gerum
  -- strict thread matches above, loose matches on Subject: below --
2010-10-23 14:54 edward.robbins
2010-10-23 15:37 ` Gilles Chanteperdrix
2010-10-23 16:21   ` edward.robbins
2010-10-23 16:26     ` edward.robbins
2010-10-23 18:46       ` edward.robbins
2010-10-23 21:52         ` Gilles Chanteperdrix
2010-10-24 15:55           ` edward.robbins
2010-10-23 16:13 ` Gilles Chanteperdrix
2010-10-23 16:22   ` Gilles Chanteperdrix

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=1287832106.517512323@domain.hid \
    --to=edward.robbins@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.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.