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: Wed, 6 Jan 2010 16:27:59 -0600 [thread overview]
Message-ID: <20100106162759.1d4d5b57@torg> (raw)
In-Reply-To: <4B450D91.7060403@osadl.org>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Wed, 06 Jan 2010 23:24:17 +0100
Carsten Emde <Carsten.Emde@osadl.org> wrote:
> Clark,
>
> >> [..]
> >> Here is my proposal:
> >> Do not change the meaning of existing options. Introduce a new option
> >> that is mutual exclusive with the -a, the -t and the -d option. This new
> >> option does the same as -a and -t and -d0 and sets the same priority to
> >> all threads. How about that?
> > Ugh, I truly *hate* adding options. Do you know that cyclictest is
> > halfway to having as many options as 'ls'?
> Well, yes, we have the choice between two bad things, breaking
> compatibility or adding another option. I prefer the latter.
Ok, I yield() :)
> > [..]
> > How about if we create the -S/--smp option that takes no arguments and
> > causes -a, -t and -d to be ignored (with a warning). This option would
> > create one thread per cpu, each thread pinned to it's corresponding
> > cpu, all with the same sampling interval (i.e. -d0) and the same
> > priority?
> Sounds good to me.
>
> May I ask you to also include the -n option which is almost always
> needed? This would then give:
>
> -S --smp Standard SMP testing (equals -a -t -n -d0),
> same priority on all threads.
>
> Carsten.
Yeah, you read my mind. How about -m (mlockall) as well?
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-06 22:28 UTC|newest]
Thread overview: 15+ 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 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 [this message]
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
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=20100106162759.1d4d5b57@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).