From: Johannes Bauer <hannes_bauer@aon.at>
To: Peter Zijlstra <peterz@infradead.org>, hannes_bauer@aon.at
Cc: Monica Puig-Pey <puigpeym@unican.es>,
Rolando Martins <rolando.martins@gmail.com>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
tglx <tglx@linutronix.de>
Subject: Re: Changing Kernel thread priorities
Date: Tue, 7 Jun 2011 10:27:35 +0200 (CEST) [thread overview]
Message-ID: <17185480.5304.1307435255996.JavaMail.root@WARSBL214.highway.telekom.at> (raw)
Absolutly correct!
However, if you are running the system on an embedded platform, where the _WHOLE_ system (including priorities) is preconfigured and never touched, starting a irq thread with the right prio from start is a more straightforward method than having to invoke a script that changes it using userspace chrt tool.
Regards JB
----- Ursprüngliche Nachricht -----
Von: "Peter Zijlstra" <peterz@infradead.org>
Erhalten: 07.06.2011 00:36
An: hannes_bauer@aon.at
"Monica Puig-Pey" wrote:
>
> I need to change the priority from inside the driver, when creating the
> kernel thread.
No you don't. How does you driver know about what priority is correct
wrt all the other running RT tasks on the system?
Determining the right priority in a fixed priority scheduling system is
a system wide problem, nobody but the administrator can possibly even
begin to solve it.
There's a reason all RT irq threads are started at 50, its plain
impossible to do better.
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-06-07 8:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 8:27 Johannes Bauer [this message]
2011-06-07 8:41 ` Thomas Gleixner
2011-06-07 9:40 ` Armin Steinhoff
2011-06-07 9:37 ` Peter Zijlstra
2011-06-07 11:02 ` Remy Bohmer
2011-06-07 14:14 ` Peter Zijlstra
2011-06-07 14:57 ` Lucas De Marchi
2011-06-07 15:15 ` Thomas Gleixner
2011-06-07 23:38 ` Nicholas Mc Guire
2011-06-07 23:35 ` Nicholas Mc Guire
2011-06-08 17:50 ` Remy Bohmer
2011-06-08 19:49 ` Thomas Gleixner
2011-06-10 14:04 ` Remy Bohmer
2011-06-10 15:37 ` Thomas Gleixner
2011-06-11 17:16 ` Remy Bohmer
2011-06-09 11:19 ` Nicholas Mc Guire
[not found] <17185480.5304.1307435255996.JavaMail.root@WARSBL214.highway.tel ekom.at>
[not found] ` <17185480.5304.1307435255996.JavaMail.root@WARSBL214.highway.te lekom.at>
2011-06-07 8:32 ` Monica Puig-Pey
2011-06-07 8:43 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 12:10 Johannes Bauer
2011-06-06 22:36 ` Peter Zijlstra
2011-06-04 11:48 One Interrupted Threads per Interrupt line? Monica Puig-Pey
2011-06-04 12:03 ` I/O operations priority in RTOS Monica Puig-Pey
2011-06-04 12:30 ` kernel threads in drivers using the RT patch Monica Puig-Pey
2011-06-06 11:47 ` Changing Kernel thread priorities Monica Puig-Pey
2011-06-06 11:54 ` Rolando Martins
2011-06-06 11:58 ` Monica Puig-Pey
2011-06-06 16:49 ` Mark Hounschell
2011-06-07 8:40 ` Monica Puig-Pey
2011-06-07 9:14 ` Mark Hounschell
2011-06-07 9:46 ` Mark Hounschell
2011-06-07 18:34 ` Monica Puig-Pey
2011-06-07 18:55 ` Mark Hounschell
2011-06-10 10:12 ` Monica Puig-Pey
2011-06-06 18:20 ` Armin Steinhoff
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=17185480.5304.1307435255996.JavaMail.root@WARSBL214.highway.telekom.at \
--to=hannes_bauer@aon.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=puigpeym@unican.es \
--cc=rolando.martins@gmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®