read here -> http://en.wikipedia.org/wiki/Preemption_%28computing%29
Time slice The period of time for which a process is allowed to run in a preemptive multitasking system is generally called the *time slice*, or *quantum*. The scheduler is run once every time slice to choose the next process to run. If the time slice is too short then the scheduler will consume too much processing time. An interrupt <http://en.wikipedia.org/wiki/Interrupt> is scheduled to allow the operating system <http://en.wikipedia.org/wiki/Operating_system> kernel<http://en.wikipedia.org/wiki/Kernel_%28computer_science%29>to switch between processes when their time slices expire, effectively allowing the processor’s time to be shared between a number of tasks, giving the illusion that it is dealing with these tasks simultaneously, or concurrently. The operating system which controls such a design is called a multi-tasking system. On Sat, May 1, 2010 at 5:26 PM, praba garan <prabagara...@gmail.com> wrote: > @ Guillermo Garcia > > Suppose a user program is executing and and clock interrupt arrives.. > Then who receives the interrupt?? > Can you xplain me the clock interrupt(like any hardwares involved) bit > detailed?? > > With Regards, > Prabagaran. > > > > On Sun, May 2, 2010 at 1:38 AM, Guillermo Garcia <gegarci...@gmail.com>wrote: > >> The scheduler takes control with a clock interruption. Then it analyzes if >> it has to preempt or not the running task. >> >> On Sat, May 1, 2010 at 5:00 PM, praba garan <prabagara...@gmail.com>wrote: >> >>> Hi all, >>> I have a doubt in OS. >>> The scheduler does the process of preemption. >>> And one processor can run atmost 1 instruction at a time. >>> Then how & where does the scheduler run?? >>> >>> With Regards, >>> Prabagaran. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Algorithm Geeks" group. >>> To post to this group, send email to algoge...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> algogeeks+unsubscr...@googlegroups.com<algogeeks%2bunsubscr...@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/algogeeks?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Algorithm Geeks" group. >> To post to this group, send email to algoge...@googlegroups.com. >> To unsubscribe from this group, send email to >> algogeeks+unsubscr...@googlegroups.com<algogeeks%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/algogeeks?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Algorithm Geeks" group. > To post to this group, send email to algoge...@googlegroups.com. > To unsubscribe from this group, send email to > algogeeks+unsubscr...@googlegroups.com<algogeeks%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/algogeeks?hl=en. > -- You received this message because you are subscribed to the Google Groups "Algorithm Geeks" group. To post to this group, send email to algoge...@googlegroups.com. To unsubscribe from this group, send email to algogeeks+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/algogeeks?hl=en.
