Changes between Version 4 and Version 5 of Design

Timestamp:

Jun 30, 2006, 6:00:41 PM (18 years ago)

Author:

soujak

Comment:

--

Design

@@ -47 +47 @@
 Designing Phase 2, we distinguished between two strictly correlated operations: scheduling and dispatching. In fact we intend the first as the action of analyzing ready processes and then choose one for execution, together with its time-quantum length. On the other hand, dispatching means to put into effect (and guarantee) that decision, that is loading the right processor state.
 
-Therefore we divided them, [wiki:Architecture#a2.2.Phase2 confining] the '''scheduler''' in a capsule which obfuscates its real implementation details. This highly increase scheduler adaptability, easing future changes in every scenarios.
+Therefore we divided them, [wiki:Architecture#a2.2.Phase2 confining] the scheduler in a capsule which obfuscates its real implementation details. This highly increase scheduler '''adaptability''', easing future changes in every scenarios.
 Moreover our implementation is oriented to run-time changes of scheduling algorithm, in order to provide an operating system that is ''general''-purpose and not ''generic''-purpose.
 In fact the scheduler's interface consist of a series of pointers to the specific-implementation functions. They are initialized by `initSched()` according to the configuration chosen in the [source:trunk/phase2/Makefile Makefile].
@@ -53 +53 @@
 
 === Dispatching ===
-We did not spend less time accurately defining interface and duties of dispatcher. In addition to the classic implementation mentioned above, we decided to request it CPU time accounting. It has to measure both direct and indirect use of the CPU. We refer to the direct use when the CPU is busied with tasks _of_ the process; indirect use qualifies the complex of tasks performed _for_ a process by the nucleus. Dispatcher itself could perform direct CPU time measure trivially, so we opted to request it also the indirect time accounting. In fact the two functions added to dispatcher interface, `play()` and `pause()`, achieve this purpose. See the diagram right above to deep understand interactions between scheduler, dispatcher and the remaining sections of the nucleus.
+We did not spend less time accurately defining interface and duties of dispatcher. In addition to the classic implementation mentioned above, we decided to request it CPU '''time accounting'''. It has to measure both direct and indirect use of the CPU. We refer to the direct use when the CPU is busied with tasks ''of'' the process; indirect use qualifies the complex of tasks performed ''for'' a process by the nucleus. Dispatcher itself could perform direct CPU time measure trivially, so we opted to request it also the indirect time accounting. In fact the two functions added to dispatcher interface, `play()` and `pause()`, achieve this purpose. See the diagram right above to deep understand interactions between scheduler, dispatcher and the remaining sections of the nucleus.
 
 {{{