Messages in this thread | | | Date | Tue, 7 Jun 2011 10:27:35 +0200 (CEST) | From | Johannes Bauer <> | Subject | Re: Changing Kernel thread priorities |
| |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |