diff --git a/LDP/guide/docbook/lkmpg-2.4/09-BlockingProcesses.sgml b/LDP/guide/docbook/lkmpg-2.4/09-BlockingProcesses.sgml index 0ddd7583..916d026b 100644 --- a/LDP/guide/docbook/lkmpg-2.4/09-BlockingProcesses.sgml +++ b/LDP/guide/docbook/lkmpg-2.4/09-BlockingProcesses.sgml @@ -36,7 +36,7 @@ When a process is done with the file, it closes it, and module_close is called. That function wakes up all the processes in the queue (there's no mechanism to only wake up one of them). It then returns and the - process which just closed the file can continue to run. In time, the scheduler decides that that process has had enough + process which just closed the file can continue to run. In time, the scheduler decides that the process has had enough and gives control of the CPU to another process. Eventually, one of the processes which was in the queue will be given control of the CPU by the scheduler. It starts at the point right after the call to module_interruptible_sleep_onThis means that the process is still in kernel mode --