Shared interrupts and RT question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I have a machine that puts several interrupts on one interrupt
line. As these are generally headless embedded machines bought
and installed by the customer, it is a bit problematic to tweak
the BIOS to assign them in an optimal way.

Now I am seeing latencies such as

Wakeup shared prio
385 50 638 (0) irq/15-eth1 <- 28 50 irq/15-ata_piix 5147.373113
#Minimum latency: 1 microseconds
#Average latency: 4 microseconds
#Maximum latency: 638 microseconds

I don't care about the ATA, but eth1 is important. Is it
enough to adjust the priorities of the kernel threads
or are shared interrupts generally a recipe for problems
in the RT_FULL world?

If there is any docs discussing the principles of interrupt
handling in a RT kernel, I'd appreciate a pointer.

Thanks
-- 
                                        Stano
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux