On Fri, Dec 09, 2005 at 14:53:01 +0530, Saumender Dash wrote: > > read in linux device driver that don't call schedule() function > >nside an interrupt handler routine but much information is not given on > >hat. so can anybody plz explain me the reason for that. > > schedule() function can sleep, that's why it's should not be called from an interrupt context. Well, sleeps means "current schedulable entity is taken off the cpu and another is made to run". Now the interrupt code does not run on behalf of a schedulable entity, so it does not have anything to put to sleep. Not that schedule() is *the* function that sleeps. Every other function that can seleep calls schedule inside. -- Jan 'Bulb' Hudec <bulb@xxxxxx>
Attachment:
signature.asc
Description: Digital signature
