programmingToolBox oper_systems -- operating systems class notes : open source web directory

return to: http:/www.sirfsup.com /programmingToolBox /oper_systems

sub-categories and articles

3733

add

PSJF_advanced process simulator shows when PSJF is better than SJF

PSJF_advanced2 failed attempt to use complicated experiments and run sheets for the process simulator

PSJF_basic gannt charts of PSJF versus SJF; used java process simulator

PSJF_better PSJF better than SJF in these cases because it doesn't let the longer, less cpu time one run at all.

rec

add

rec8

add

simulator

add

unix_c unix c system calls and programming: pipes, fd, sockets, threads

--->create new sub-category

connection_communication.txt

add

moved it all over to thanks delete after one year forgetful

context_switch_time.html

add

critical.txt

add

critical sections

disk_head_scheduling.txt

add

algorithms for disk access ========================== silberschatz one page how is IO scheduled

filesystems.txt

add

see http://www.cim.mcgill.ca/~franco/OpSys-304-427/lecture-notes/node27.html

final.txt

add

question on interpreting the critical section by looking at the code, tell how it works like it does final exam operating systems 3343 ================================= write a signal handler which ignores a signal

linux_scheduling.txt

add

scheduling ========== quantum =======

load_average.html

load_average = total_wait_time / total_run_time

memory.txt

TLB virtaul memory physical memory translation

memory.txt

memory_advanced.txt: memory_advanced.txt
relocatable_modules.txt: relocatable_modules.txt

memory_advanced.txt

linux specific memory management from "linux kernel" book

memory addressing not covered in class

memory.txt: memory management excluding the below
relocatable_modules.txt: compiling, linking, loading

midterm1.txt

add

midterm1 ======== emphasis on concepts not on code (but see below for notes on knowing syntax of read/write functions) diff bw buffering and spooling as far as basic OS are concerned

monitor.txt

add

monitors ======== hard to understand. After having studied semaphores and critical sections, lots of stuff of monitors is different. monitors are like classes but

movements.txt

add

rec7 was moved to /unix_c/pipes/token_ring connection_communication.txt moved to /languages/c/unix_c/socket_libs/uici/ signals.txt moved to /languages/c/unix_c/signals/signals.txt semaphore section of critical.txt to /languages/c/unix_c/sem/sem.txt

mutex.txt

add

mutexes ======= for mutex discussion, deal with their application not their, uh, how-they-work mutexes and semaphores

openbsd.glob.c

add

/*

program_mem_addresses.txt

add

how programs manage memory: 1. memory references are symbolic 2. symbolic references must be changed 3. compiler responsible for some of the binding process.

relocatable_modules.txt

compilers linking loading dynamic loading

relocatable program modules

memory_advanced.txt: memory_advanced.txt
memory.txt: memory.txt
programs_mem relocatable program modules
when does address translation take place
loading dynamically
linking dynamically

scheduling.txt

process scheduling algorithms used by the cpu

wait_time_loadAvg.txt

add

1. dont set duration less than cpu bursts this will not work :) 2. PSJF has avg wait time 50% less than SJF given when: answer: part 3a: PSJF will do better than SJF if a short job (small CPU burst) enters the ready queue when a long job (large remaining CPU burst) is running. The short processes will have to wait. If the long job is not preempted all the short CPU bursts must wait for the longer burst to finish. 3c. parameters required to know:

--->upload your article

User submitted category site links

(None)

-->submit a page from your site dealing with oper_systems to the sirfsup! web directory for listing

return to top