From: Nicholas Mc Guire <der.herr@hofr.at>
To: linux-rt-users@vger.kernel.org
Subject: cyclictest problem/bug as non-root
Date: Fri, 10 Feb 2012 12:57:21 +0100 [thread overview]
Message-ID: <20120210115721.GA13313@opentech.at> (raw)
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
diff --git a/src/cyclictest/cyclictest.c b/src/cyclictest/cyclictest.c
index 731b4bd..fa89502 100644
--- a/src/cyclictest/cyclictest.c
+++ b/src/cyclictest/cyclictest.c
@@ -33,6 +33,7 @@
#include <sys/time.h>
#include <sys/utsname.h>
#include <sys/mman.h>
+#include <sys/resource.h>
#include "rt_numa.h"
#include "rt-utils.h"
@@ -641,7 +642,10 @@ void *timerthread(void *param)
memset(&schedp, 0, sizeof(schedp));
schedp.sched_priority = par->prio;
- sched_setscheduler(0, par->policy, &schedp);
+ if(sched_setscheduler(0, par->policy, &schedp) == -1){
+ fprintf(stderr,"sched_setscheduler prio %d failed\n",par->prio);
+ par->prio=0;
+ }
/* Get current time */
clock_gettime(par->clock, &now);
@@ -943,6 +947,7 @@ static void process_options (int argc, char *argv[])
{
int error = 0;
int max_cpus = sysconf(_SC_NPROCESSORS_CONF);
+ struct rlimit rlim;
for (;;) {
int option_index = 0;
@@ -1145,6 +1150,15 @@ static void process_options (int argc, char *argv[])
policy = SCHED_FIFO;
}
+ /* check against rlimit see /etc/security/limits.conf */
+ getrlimit(RLIMIT_RTPRIO, &rlim);
+ if ( priority > rlim.rlim_max){
+ fprintf(stderr, "defaulting realtime priority to %d\n",
+ (int) rlim.rlim_max);
+ priority = rlim.rlim_max;
+ }
+
+
if ((policy == SCHED_FIFO || policy == SCHED_RR) && priority == 0) {
fprintf(stderr, "defaulting realtime priority to %d\n",
num_threads+1);
next reply other threads:[~2012-02-10 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 11:57 Nicholas Mc Guire [this message]
2012-02-11 15:45 ` cyclictest problem/bug as non-root Clark Williams
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=20120210115721.GA13313@opentech.at \
--to=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).