Home › GATE CSE › computerscience › Operating Systems › Which of the following is NOT typically minimise…
Which of the following is NOT typically minimised by a CPU scheduler?
AAverage turnaround time
BAverage response time
CCPU utilisation (kept HIGH)
DThe OS kernel's own memory footprint
Answer & Solution
Correct answer: D. The OS kernel's own memory footprint
1. OSTEP §7.1 lists the typical scheduling metrics.
2. Schedulers typically aim to:
- MINIMISE average turnaround time (faster job completion)
- MINIMISE average response time (faster interactivity)
- MAXIMISE CPU utilisation (keep CPU busy)
3. The kernel's memory footprint is a DIFFERENT concern (handled by kernel implementation, not the scheduler).
4. So option D is the odd one out.
5. (Caveat: kernel scheduler overhead is sometimes considered; but kernel total memory size is not a scheduling metric.)
_Source: OSTEP Ch 7, §7.1 (Scheduling Metrics — list), p. 1-2._
Related questions
On a MULTI-CORE system, a SPIN LOCK is generallyDisabling INTERRUPTS as a way to implement mutual exclusion on a single-CPU system isA LIVELOCK differs from a DEADLOCK in thatSuppose thread A acquires lock L1, then thread B acquires lock L2. Now A tries to acquire Without atomic hardware support, building a correct mutual-exclusion lock for $N \geq 2$ tA CRITICAL SECTION isLinux's `pthread_mutex_lock()` is typically implemented as a HYBRID:What is the PRIMARY problem with using a SPIN LOCK on a SINGLE-CPU uniprocessor system (wi