Bug 747751 - 3.2. Processor Scheduling
Summary: 3.2. Processor Scheduling
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: musicians-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Antila
QA Contact: Nobody's working on this, feel free to take it
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-20 22:20 UTC by Jonquil
Modified: 2013-01-19 17:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-19 17:57:32 UTC


Attachments (Terms of Use)

Description Jonquil 2011-10-20 22:20:57 UTC
3.2. Processor Scheduling
If you've ever opened the "System Monitor" application you will probably have noticed that there are a lot of "processes" running all the time. Some of these processes need the processor and some of them are just waiting around for something to happen. To help increase the number of processes that can run at the same time many modern CPUs have more than one "core," which allows for more processes to be evaluated at the same time. Even with these improvements there are usually more processes than available cores: my computer right now has 196 processes and only three cores. There has to be a way of decided which process gets to run and when and this task is left to the operating system.
In Linux systems like Fedora the core of the operating system (called the kernel) is responsible for deciding which process gets to execute at what time. This responsibility is called "scheduling." Scheduling access to the processor is called, processor scheduling. The kernel also manages scheduling for a number of other things like memory access, video hardware access, audio hardware access, hard drive access, and so on. The algorithm (procedure) used for each of these scheduling tasks is different for each and can be changed depending on the user's needs and the specific hardware being used. In a hard drive, for example, it makes sense to consider the physical location of data on a disk before deciding which process gets to read first. For a processor this is irrelevant but there are many other things to consider.
There are a number of scheduling algorithms that are available with the standard Linux kernel and for most uses a "fair queueing" system is appropriate. This helps to ensure that all processes get an equal amount of time with the processor and it's unacceptable for audio work. If you're recording a live concert and the "PackageKit" update manager starts you don't care if PackageKit gets a fair share of processing time - it's more important that the audio is recorded as accurately as possible. For that matter, if you're recording a live concert and your computer isn't fast enough to update the monitor, keyboard, and mouse position while providing uninterrupted, high-quality audio you want the audio instead of the monitor, keyboard, and mouse. After all, once you've missed even the smallest portion of audio it's gone for good!

Comment 1 Christopher Antila 2011-10-25 01:03:33 UTC
Another batch of terrific revisions. Thank you!

Comment 2 Karsten Wade 2011-12-14 03:48:16 UTC
Removing myself for these bug components as I'm either no longer involved in that aspect of the project, or no longer care to watch this particular bug. Sorry if you are caught in a maelstrom of bug changes as a result!

Comment 3 Christopher Antila 2012-08-25 21:46:37 UTC
Fix to be pushed as commit 67a8de94b1a1614880b31f570a2468307a81b21c

Comment 4 Christopher Antila 2013-01-19 17:57:32 UTC
Fixed with publication for Fedora 18:

https://docs.fedoraproject.org/en-US/Fedora/18/html/Musicians_Guide/index.html


Note You need to log in before you can comment on or make changes to this bug.