home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!haven.umd.edu!wam.umd.edu!joel
- From: joel@wam.umd.edu (Joel M. Hoffman)
- Subject: Re: Linux Scheduling (Was Re: Die Die Die) (long)
- Message-ID: <1993Jan2.200014.1687@wam.umd.edu>
- Sender: usenet@wam.umd.edu (USENET News system)
- Nntp-Posting-Host: rac2.wam.umd.edu
- Organization: University of Maryland, College Park
- References: <BzM129.Lp@brunel.ac.uk> <1992Dec21.155544.20713@mcs.gvsu.edu>
- Date: Sat, 2 Jan 1993 20:00:14 GMT
- Lines: 26
-
- In article <1992Dec21.155544.20713@mcs.gvsu.edu> wissner@perlis.mcs.gvsu.edu (Jim Wissner) writes:
- >The Linux scheduler follows (in general) a round-robin scheduling model,
- >in that each process initially gets a fixed time quantum. Of course, if
- >a process uses up its quantum it is preempted, and if it needs to sleep
- >while doing some sort of IO, it releases the CPU voluntarily.
- >
- >[...]
- >And theoretically, the scheme Linux uses shouldn't allow for starvation
- >(what you are experiencing) - processes that use their quantum will
- >'wait' until all other processes have had their chance. There is,
- >however, no mechanism to /prevent/ starvation. This is what I suspect
- >[...]
-
- That's where ``nice'' levels should help. What happens with a process
- with the highest possible nice level (or lowest, I forget which way
- Linux does it)? Will it also give up its time to any new process? I
- like to have ``top'' running as root on one VC, so I can control the
- system if need be. Why not put new processes as close to the front of
- the queue as possible without putting them ahead of any processes with
- higher nice values. Of course, that involves more overhead for
- creating a new process, but it would ensure that new processs can't
- starve high nice-level ones.
-
- -Joel
- (joel@wam.umd.edu)
-
-