linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: cyclictest problem/bug as non-root
Date: Sat, 11 Feb 2012 09:45:59 -0600	[thread overview]
Message-ID: <20120211094559.0a0edcb1@redhat.com> (raw)
In-Reply-To: <20120210115721.GA13313@opentech.at>

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

On Fri, 10 Feb 2012 12:57:21 +0100
Nicholas Mc Guire <der.herr@hofr.at> wrote:

> 
> HI !
> 
>  minor bug in cyclictest but potential causing confusion on cyclictest 
>  resuults when running as non-root user.
> 
> Setup:
>  if one sets the rtprio in /etc/security/limits.conf to something below
>  prio max - like:
> 
>  @hofrat          hard    rtprio          10
>  @hofrat          soft    rtprio          10
> 
>  but then starts cylictest with -p 80 cyclictest will not fuss and also
>  display priority 80 (as it uses par->prio in print_stat) but effectively 
>  runs with prio 0 as the return value of sched_setscheduler is not being
>  checked in timerthread), resulting in semingly bad scheduling jitter values.
> 
>  So maybe cyclictest should take the effective maximum schduling priority
>  of the user and not the scheduling policy maximum. Not sur if the check
>  in timerthread is actually really needed - but it should not hurt ither.
>  patch below (against current git) at "works for me" quality.
> 
> thx!
> hofrat
> 
> 

Thanks Nicholas, I'll apply it and run it through some tests. Looks
good at first glance though.

Clark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-02-11 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 11:57 cyclictest problem/bug as non-root Nicholas Mc Guire
2012-02-11 15:45 ` Clark Williams [this message]
2012-05-09 13:19 ` John Kacur

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=20120211094559.0a0edcb1@redhat.com \
    --to=williams@redhat.com \
    --cc=der.herr@hofr.at \
    --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).