From: Clark Williams <williams@redhat.com>
To: Carsten Emde <Carsten.Emde@osadl.org>
Cc: John Kacur <jkacur@redhat.com>,
RT <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [rt-tests] change to cyclictest behavior
Date: Thu, 7 Jan 2010 08:47:00 -0600 [thread overview]
Message-ID: <20100107084700.0fa053a3@torg> (raw)
In-Reply-To: <4B458C08.8070209@osadl.org>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Thu, 07 Jan 2010 08:23:52 +0100
Carsten Emde <Carsten.Emde@osadl.org> wrote:
> Clark,
>
> >> -S --smp Standard SMP testing (equals -a -t -n -d0),
> >> same priority on all threads.
> After having done some tests with a quickly hacked cyclictest version, I
> have found an issue with including -d0. Apparently, small numbers make
> life especially difficult for the scheduler; this is why we often used
> -d1. Specifying -d0 seems a special case where all threads are in sync.
> Maybe, we may miss some important latency constellations, if we do not
> let the tasks slightly interfere. In any case, I would like to be able
> to specify a distance _in addition_ to -S. This would create a scenario
> where
>
> cyclictest -d1 -S
>
> results in a distance of 0, and
>
> cyclictest -S -d1
>
> results in a distance of 1. Would this be acceptable?
>
> Carsten.
I don't have a problem not having -d in the -S option. I was looking at
the possibility of synchronous sampling as well so it's probably a good
idea to keep it separate.
The main things we want are implied -t, -a and -n.
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-07 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 19:04 [RFC] [rt-tests] change to cyclictest behavior Clark Williams
2010-01-06 19:39 ` John Kacur
2010-01-06 19:39 ` John Kacur
2010-01-06 21:39 ` Carsten Emde
2010-01-06 22:04 ` Clark Williams
2010-01-06 22:24 ` Carsten Emde
2010-01-06 22:27 ` Clark Williams
2010-01-06 22:50 ` Carsten Emde
2010-01-07 0:30 ` Leyendecker, Robert
2010-01-07 7:09 ` Carsten Emde
2010-01-07 7:23 ` Carsten Emde
2010-01-07 14:47 ` Clark Williams [this message]
2010-01-07 14:54 ` Carsten Emde
2010-01-12 16:59 ` Sven-Thorsten Dietrich
2010-01-12 17:04 ` Clark Williams
2010-01-12 17:13 ` Sven-Thorsten Dietrich
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=20100107084700.0fa053a3@torg \
--to=williams@redhat.com \
--cc=Carsten.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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.