Messages in this thread | | | Subject | Re: [RFC] Summit interrupt routing patches | Date | Fri, 18 Jan 2002 23:15:41 +0000 (GMT) | From | Alan Cox <> |
| |
> alternative is much more invasive: adding interrupt code to adjust XTPRs, > hacks to the scheduler to somehow encapsulate task priority in 4 bits, etc.
Is it necessary to try something complex. We already keep per cpu/per irq data and if you have a lot of interrupts it feels like you can handwave them to be roughly the same amount of cpu load.
Given that is it enough to once a second shuffle the irqs around to try and get a rough balance based on a simple decaying history. Then all it needs is a regular timer event to do what the hardware hasnt
- 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/
| |