Understanding non-preemptive kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
 
I want to to check my understanding about a non-preemptive kernel like 2.4.
 
Please let me know if anything is wrong with the below.
 
Suppose a process 1 is in kernel mode. Unless it calls schdeule() voluntarily, it should not be interleaved with another kernel path ( except in case of interrupts and exceptions ). If it is interrupted, then it should be continued after the interrupt handler is done.
What happens in the case of timer interrupt ?
I understand that once the time slice is over, the timer interrupt happens and the interrupt handler calls schedule() to schedule another process. But what happens in this case ? the handler does not call schedule() , and enables the current process to continue till it voluntarily relinqueshes the CPU ?
 
Thanks,
Rajaram.
 
 


Yahoo! Autos. Looking for a sweet ride? Get pricing, reviews, & more on new and used cars.

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux