Re: Question on Schedule and Preemption

[Andreas Mohr]

Hi,

On Tue, Apr 18, 2006 at 11:23:47AM +0200, Arjan van de Ven wrote:
> 
> > If the current task is running and thus not yet exiting (!current->exit_state)
> > and is also in an atomic code section (i.e. under lock), it shouldn't call
> > any reschedule function (which also happens by just calling msleep(): use
> > mdelay() instead in that case!).
> > 
> 
> actually don't use mdelay, but change your code so that you CAN sleep :)

Ermm, I meant to say that, but forgot to do so clearly, sorry.

Basically long delays while holding locks are also a very baaad thing,
thus always avoid delays as much as possible there.

Andreas Mohr

-- 
No programming skills!? Why not help translate many Linux applications! 
https://launchpad.ubuntu.com/rosetta
(or alternatively buy nicely packaged Linux distros/OSS software to help
support Linux developers creating shiny new things for you?)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/