> > I must have missed that in the code. I can see you check __cli() status but > > I didn't see anywhere you check disable_irq(). Even if you did it doesnt > > help when I mask the irq on the chip rather than using disable_irq() calls. > > But you get interrupted by other interrups then so you have the same problem > reagardless of any preemtion patch you hopefully lose the cpu for a much > shorter time but still the same problem. Interrupt paths are well sub millisecond, a pre empt might mean I don't get the CPU back for measurable chunks of a second. They are totally different guarantees. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- Re: [2.4.17/18pre] VM and swap - it's really unusableKenneth Johansson <ken _at_ canit.se>
- Prev by Date: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Next by Date: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Previous by thread: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Next by thread: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Indexes:[Main][Thread]