--
When I'm asked what language is my mother tongue,
I simply answer C.
On Fri, 10 Aug 2007, Remy Bohmer wrote:
Hello Darren, Juergen and Ingo,
Maybe Ingo can look at it, and find a way to implement it more
generic? (In the softirq_info struct we could default set all prios
back to 50, and
Hello Steven,
Actually, the handler thread runs _all_ register interrupt handlers. So
there's no way to make one a higher priority than the other. This is a
tough problem. If you have two shared handlers on the same irq line,
and think you can make one a higher priority than the other, you
Hello Steven,
Perhaps adding in a new command line interface (We may need to extend the
command line size limit). Where one could do
irq_priority_map=10-51,21-40,... Where the first number is the irq number
followed by the irq priority. We can also do something similar to
softirqs.
Would
Hello Darren, Juergen and Ingo,
All I need is one IRQ at priority 51, all other can still run at 50. And I
don't want to search at system's runtime for the right PID of driver's
thread to set its priority via chrt. There is no user at this system, its
an embedded one.
It seems
--
On Fri, 10 Aug 2007, Remy Bohmer wrote:
Hello Steven,
Perhaps adding in a new command line interface (We may need to extend the
command line size limit). Where one could do
irq_priority_map=10-51,21-40,... Where the first number is the irq number
followed by the irq priority. We
Hello Darren,
I disagree. The point of real-time is to provide user-space with more control
of what get's run, when, instead of something else - including system
interrupts, etc. For instance, if networking should take a higher priority
than their application, but disk i/o should take a
Darren,
On Wednesday 08 August 2007 23:09, Darren Hart wrote:
On Wednesday 08 August 2007 06:14:31 you wrote:
Hi,
with the rt-preempt patch the IRQs are all kernelthreads started with
priority 50. Is there a way to change this priority from inside the
driver, after I did the
On Thursday 09 August 2007 07:10:57 Juergen Beisert wrote:
Darren,
On Wednesday 08 August 2007 23:09, Darren Hart wrote:
On Wednesday 08 August 2007 06:14:31 you wrote:
Hi,
with the rt-preempt patch the IRQs are all kernelthreads started with
priority 50. Is there a way to change
On Wednesday 08 August 2007 06:14:31 you wrote:
Hi,
with the rt-preempt patch the IRQs are all kernelthreads started with
priority 50. Is there a way to change this priority from inside the driver,
after I did the request_irq() call? I need a higher priority for one
interrupt source but I do
