> The file locking use real IO and so when you ask for a lock, if the loc= > k is already owned, you fall in a D state. That seems odd. They should be using interruptible sleeps so you can interrupt the task waiting for the lock, surely. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Re: uninteruptable sleep Stephen E. Clark
- Re: uninteruptable sleep Anton Blanchard
- Re: uninteruptable sleep Alan Cox
- Re: uninteruptable sleep Trevor Nichols
- Re: uninteruptable sleep J Sloan
- Re: uninteruptable sleep Trevor Nichols
- Re: uninteruptable sleep andersg
- Re: uninteruptable sleep Christian Pernegger
- Re: uninteruptable sleep Manfred Spraul
- Re: uninteruptable sleep (D state => load_avrg... christophe barbe
- Re: uninteruptable sleep (D state => load_... Alan Cox
- Re: uninteruptable sleep (D state => l... christophe barbe
- Re: uninteruptable sleep (D state =&g... Alan Cox
- Re: uninteruptable sleep (D state =&g... Paul Jakma
- Re: uninteruptable sleep (D stat... christophe barbe
- Re: uninteruptable sleep (D ... Paul Jakma
- Re: uninteruptable sleep (D ... christophe barbe
- Re: uninteruptable sleep (D state =&g... Tim Wright
- Re: uninteruptable sleep christophe barbe