![]() | |||||||||||||
Messages in this thread |
Fabiano Ramos wrote: > Hi all. > > I am in doubt about the linux kernel behaviour is this situation: > supose a have the process A, with the highest realtime > priority and SCHED_FIFO policy. The process then issues a syscall, > say read(): > > 1) Can I be sure that there will be no process switch during the > syscall processing, even if the system call causes a page fault? A page fault means your realtime process must wait, because the data it wants isn't available yet. (Data have to be fetched from disk/device which takes lots of time.) There is nothing wrong with handing the cpu to some other lower priority process unser such circumstances, because your realtime process are stuck and can't use it anyway. The realtime process wil grab the cpu as soon as it gets ready to run anyway, I believe the scheduler looks for this sort of thing when the pagefault eventually completes. Helge Hafting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:02 [from the cache] ©2003-2008 | |||||||||||||