operating systems are an essential part of any computer system. similarly, a course on operating systems is an essential part of any computer science education. this field is undergoing rapid change, as computers are now prevalent in virtually every arena of day-to-day life—from embedded devices in automobiles through the most sophisticated planning tools for governments and multinational firms. yet the fundamental concepts remain fairly clear, and it is on these that we base this course.
jinan university fulltimeundergraduate program course de___scription
course offered by: international school student type: computer science
credits: 3.5 hrs./week: 3 total hrs. 63
course title | operating systems | ||||||||||||||||||||||||||||
previous course title | |||||||||||||||||||||||||||||
course code | 60080015 | course type | compulsory | ||||||||||||||||||||||||||
prerequisite course(s) | c,java, problem solving and programming | course evaluation | exam | ||||||||||||||||||||||||||
(teaching objectives、teaching requirements、teaching contents) 1. teaching objectives "operating system" is a computer professional and compulsory basic course. it is a technical and practical course. this course will enable students to fully grasp the exclusive formation and development of the operating system, processor memory management, device management, operations management and processes, synchronization, communication and deadlock, to learn how to use windows, linux, android, other different operating systems, and to solve practical problems. 2. teaching requirements 1) describe the basic organization of computer systems 2) provide a grand tour of the major components of operating systems 3) give an overview of the many types of computing environments 4) explore several open-source operating systems 3. teaching contents
the content is organized in eight major parts: 1. overview. chapters 1 and 2 explain what operating systems are, what they do, and how they are designed and constructed. these chapters discuss what the common features of an operating system are and what an operating system does for the user. we include coverage of both traditional pc and server operating systems, as well as operating systems for mobile devices. the presentation is motivational and explanatory in nature. we have avoided a discussion of how things are done internally in these chapters. therefore, they are suitable for individual readers or for students in lower-level classes who want to learn what an operating system is without getting into the details of the internal algorithms. 2. process management. chapters 3 through 7 describe the process concept and concurrency as the heart of modern operating systems. a process is the unit of work in a system. such a system consists of a collection of concurrently executing processes, some of which are operating-system processes (those that execute system code) and the rest of which are user processes (those that execute user code). these chapters cover methods for process scheduling, interposes communication, process synchronization, and deadlock handling. also included is a discussion of threads, as well as an examination of issues related to multicore systems and parallel programming. 3. memory management. chapters 8 and 9 deal with the management of main memory during the execution of a process. to improve both the utilization of the cpu and the speed of its response to its users, the computer must keep several processes in memory. there are many different memory-management schemes, reflecting various approaches to memory management, and the effectiveness of a particular algorithm depends on the situation. 4. storage management. chapters 10 through 13 describe how mass storage, the file system, and i/o are handled in a modern computer system. the file system provides the mechanism for on-line storage of and access to both data and programs. we describe the classic internal algorithms and structures of storage management and provide a firm practical understanding of the algorithms used their properties, advantages, and disadvantages. since the i/o devices that attach to a computer vary widely, the operating system needs to provide a wide range of functionality to applications to allow them to control all aspects of these devices. we discuss system i/o in depth, including i/o system design, interfaces, and internal system structures and functions. in many ways, i/o devices are the slowest major components of the computer. because they represent a performance bottleneck, we also examine performance issues associated with i/o devices. 5. protection and security. chapters 14 and 15 discuss the mechanisms necessary for the protection and security of computer systems. the processes in an operating system must be protected from one another’s activities, and to provide such protection, we must ensure that only processes that have gained proper authorization from the operating system can operate on the ®les, memory, cpu, and other resources of the system. protection is a mechanism for controlling the access of programs, processes, or users to computer-system resources. this mechanism must provide a means of specifying the controls to be imposed, as well as a means of enforcement. security protects the integrity of the information stored in the system (both data and code), as well as the physical resources of the system, from unauthorized access, malicious destruction or alteration, and accidental introduction of inconsistency. 6. case studies. chapters 20 through 22 in the text, along with appendices a and b, present detailed case studies of real operating systems, including linux, freebsd, and mach. coverage of both linux and windows 7 are presented throughout this text; however, the case studies provide much more detail. it is especially interesting to compare and contrast the design of these two very different systems. chapter 20 briefly describes a few other influential operating systems. | |||||||||||||||||||||||||||||
text book(s) and reference materials | text book:operating systems concepts isbn: 9787040209280 higher education press reference materials: operating systems:principles and design isbn: 9787302274896, 7302274894 |
jinan university
undergraduate syllabus for
__operating systems ____ (course title)
course code 60080015
course title operating systems
course type compulsory[√ ] specialized optional [ ] common optional [ ]
prerequisites c,java,problem solving and programming
credits 3.5
total course hours 63
majors applicableto computer science
students classification mainland[√] non-mainland [√]
department/schooloffering the course internationalschool
i. teachingobjectives and requirements
"operatingsystem" is a computer professional and compulsory basic course. it is atechnical and practical course. this course will enable students to fully graspthe exclusive formation and development of the operating system, processormemory management, device management, operations management and processes,synchronization, communication and deadlock, to learn how to use windows,linux, android, other different operating systems, and to solve practicalproblems.
teachingrequirements:
1) describe the basic organizationof computer systems
2) provide a grand tour of themajor components of operating systems
3) give an overview of the manytypes of computing environments
4) explore several open-sourceoperating systems
ii. key pointsand main areas of difficulty of the course
1) organization of computersystems
2) processor memory management,device management, operations management and processes, synchronization,communication and deadlock, protection & security,
iii. lab or practical work required to support thecourse
1) elevator schedule: a buildingof 20-floors,five interconnected elevator. based multi-thread, writing anelevator scheduler.
2) banker's algorithm: processesp0 through p4;3 resource types: a (10 instances), b (5instances), and c (7instances),snapshot at time t0: can request for (1,0,2) by p1 be granted?canrequest for (0,1,0) by p2 be granted?
3) protection: please givethe rights-set matrix, and implement the management system.
4) mit’s lab
iv. textbooks and references
a) text book:operating systems concepts
isbn:9787040209280
higher education press
b) reference materials:
isbn:9787302274896, 7302274894
n conference list
no. | conference | url | ||
1 | isca | international symposium on computer architecture | acm sigarch, ieee tcca | http://www.acm.org/pubs/contents/proceedings/series/isca/ |
2 | micro | ieee, acm sigmicro | http://www.microarch.org/ | |
3 | asplos | architectural support for programming languages and operating systems | acm sigops/sigarch/sigplan | http://www.acm.org/pubs/contents/proceedings/series/asplos/ |
4 | fast | conference on file and storage technologies | usenix | http://www.usenix.org/events/bytopic/fast.html |
5 | pact | parallel architectures and compilation techniques | ieee acm sigarch | http://pact07.cs.tamu.edu/ |
6 | hpca | high-performance computer architecture | ieee | http://www.ece.arizona.edu/~hpca/ |
7 | ppopp | principles and practice of parallel programming | acm sigplan | http://research.ihost.com/ppopp08/ |
8 | spaa | acm symposium on parallelism in algorithms and architectures | acm | http://www.cs.jhu.edu/~spaa/2007/ |
9 | sigmetrics | international conference on measurement and modeling of computer systems | acm sigmetrics | http://www1.cs.columbia.edu/~sigmet08/ |
10 | rtss | real-time systems symposium | ieee | http://www.rtss.org/ |
n journals directory
v. grading system and evaluation methods
n 30%: exam
n 30%: course project(source code, run video, presentations)
(13 persons/week for two weeks, between 15nd and 16th weeks)
n 20%: exercises and participation
n 20%: paper reviews and coursepresentations(20 mins/person )
(two persons/week for 13 weeks, between 2nd and 14th weeks)
vi. detailed points of teaching contents
date / month | lesson | class hours | main contents (objectives and requirements, key points) | ||
lec- ture | lab | ||||
1 | march 3-4 | ch 1 introduction | 4 | 1.1 what operating systems do 4 1.2 computer-system organization 7 1.3 computer-system architecture 12 1.4 operating-system structure 19 1.5 operating-system operations 21 1.6 process management 24 1.7 memory management 25 1.8 storage management 26 1.9 protection and security 30 1.10 kernel data structures 31 1.11 computing environments 35 1.12 open-source operating systems 43 1.13 summary 47 | |
2 | march 10-11 | ch 2 operating-system structures | 4 | 2.1 operating-system services 55 2.2 user and operating-system interface 58 2.3 system calls 62 2.4 types of system calls 66 2.5 system programs 74 2.6 operating-system design and implementation 75 2.7 operating-system structure 78 2.8 operating-system debugging 86 2.9 operating-system generation 91 2.10 system boot 92 2.11 summary 93 | |
3 | march 17-18 | ch 3 processes | 4 | 3.1 process concept 105 3.2 process scheduling 110 3.3 operations on processes 115 3.4 interprocess communication 122 3.5 examples of ipc systems 130 3.6 communication in client– server systems 136 3.7 summary 147 4.1 overview 163 4.2 multicore programming 166 4.3 multithreading models 169 4.4 thread libraries 171 4.5 implicit threading 177 4.6 threading issues 183 4.7 operating-system examples 188 4.8 summary 191 | |
ch 4 threads | |||||
4 | -25 | ch 5 cpu scheduling | 4 | 3 | 5.1 background 203 5.2 the critical-section problem 206 5.3 peterson’s solution 207 5.4 synchronization hardware 209 5.5 mutex locks 212 5.6 semaphores 213 5.7 classic problems of synchronization 219 5.8 monitors 223 5.9 synchronization examples 232 5.10 alternative approaches 238 5.11 summary 242 |
5 | march 31-april 1 | ch 6 process synchronization ch 7 deadlocks | 4 | 6.1 basic concepts 261 6.2 scheduling criteria 265 6.3 scheduling algorithms 266 6.4 thread scheduling 277 6.5 multiple-processor scheduling 278 6.6 real-time cpu scheduling 283 6.7 operating-system examples 290 6.8 algorithm evaluation 300 6.10 summary 304 7. deadlocks 7.1 system model 315 7.2 deadlock characterization 317 7.3 methods for handling deadlocks 322 7.4 deadlock prevention 323 7.5 deadlock avoidance 327 7.6 deadlock detection 333 7.7 recovery from deadlock 337 7.8 summary 339 | |
6 | april 7-8 | ch 8 main memory | 4 | 3 | 8.1 background 351 8.2 swapping 358 8.3 contiguous memory allocation 360 8.4 segmentation 364 8.5 paging 366 8.6 structure of the page table 378 8.7 example: intel 32 and 64-bit architectures 383 8.8 example: arm architecture 388 8.9 summary 389 |
7 | april 14-15 | ch 9 virtual memory | 4 | 9.1 background 397 9.2 demand paging 401 9.3 copy-on-write 408 9.4 page replacement 409 9.5 allocation of frames 421 9.6 thrashing 425 9.7 memory-mapped files 430 9.8 allocating kernel memory 436 9.9 other considerations 439 9.10 operating-system examples 445 9.11 summary 448 | |
8 | april 21-22 | ch 10 file-system interface | 4 | 3 | 10.1 overview of mass-storage structure 467 10.2 disk structure 470 10.3 disk attachment 471 10.4 disk scheduling 472 10.5 disk management 478 10.6 swap-space management 482 10.7 raid structure 484 10.8 stable-storage implementation 494 10.9 summary 496 |
9 | april 28-29 | ch 11 file-system implementation | 4 | 11.1 file concept 503 11.2 access methods 513 11.3 directory and disk structure 515 11.4 file-system mounting 526 11.5 file sharing 528 11.6 protection 533 11.7 summary 538 | |
10 | may 5-6 | ch 12 mass-storage structure | 4 | 3 | 12.1 file-system structure 543 12.2 file-system implementation 546 12.3 directory implementation 552 12.4 allocation methods 553 12.5 free-space management 561 12.6 efficiency and performance 564 12.7 recovery 568 12.8 nfs 571 12.9 example: the wafl file system 577 12.10 summary 580 |
11 | may 12-13 | ch 13 i/o systems | 4 | 13.1 overview 587 13.2 i/o hardware 588 13.3 application i/o interface 597 13.4 kernel i/o subsystem 604 13.5 transforming i/o requests to hardware operations 611 13.6 streams 613 13.7 performance 615 13.8 summary 618 | |
12 | may 19-20 | ch 14 protection | 4 | 3 | 14.1 goals of protection 625 14.2 principles of protection 626 14.3 domain of protection 627 14.4 access matrix 632 14.5 implementation of the access matrix 636 14.6 access control 639 14.7 revocation of access rights 640 14.8 capability-based systems 641 14.9 language-based protection 644 14.10 summary 649 |
13 | may 26-27 | ch 15 security | 4 | 15.1 the security problem 657 15.2 program threats 661 15.3 system and network threats 669 15.4 cryptography as a security tool 674 15.5 user authentication 685 15.6 implementing security defenses 689 15.7 firewalling to protect systems and networks 696 15.8 computer-security classifications 698 15.9 an example: windows 7 699 15.10 summary 701 | |
14 | june 2-3 | ch 21 the linux system | 4 | 3 | 15.1 linux history 687 15.2 design principles 692 15.3 kernel modules 695 15.4 process management 698 15.5 scheduling 701 15.6 memory management 706 15.7 file systems 715 15.8 input and output 721 15.9 interprocess communication 724 15.10 network structure 725 15.11 security 727 15.12 summary 730 exercises 731 bibliographical notes 733 |
15 | june 9-10 | appendix a: bsd unix project presentation | 2 | a.1 unix history a1 a.2 design principles a6 a.3 programmer interface a8 a.4 user interface a15 a.5 process management a18 a.6 memory management a22 a.7 file system a24 a.8 i/o system a32 a.9 interprocess communication a36 a.10 summary a40 project presentation | |
16 | june 16-17 | the mach system project presentation | 2 | b.1 history of the mach system a897 b.2 design principles a899 b.3 system components a900 b.4 process management a903 b.5 interprocess communication a909 b.6 memory management a914 b.7 programmer interface a919 b.8 summary b24 a920 exercises a921 bibliographical notes a922 credits a923 project presentation | |
17 | june 23-24 | review | 2 | ||
18 | june 30 -july 1 | review | 2 | ||
19 | july7 | exam | 2 |
part 1: overview |
n chapter 1,introduction, includes updated coverage of multiprocessor and multicoresystems, as well as a new section on kernel data structures. additionally, thecoverage of computing environments now includes mobile systems and cloudcomputing. we also have incorporated an overview of real-time systems.
n chapter 2,operating-system structures, provides new coverage of user interfaces formobile devices, including discussions of ios and android, and expanded coverage of mac os x as a type of hybrid system.
overview.chapters 1 and 2 explain what operating systems are, what they do, and how theyare designed and constructed. these chapters discuss what the common featuresof an operating system are and what an operating system does for the user. weinclude coverage of both traditional pc andserver operating systems, as well as operating systems for mobile devices.
part 2: process management |
n chapter 3, processes, now includes coverage ofmultitasking in mobileoperating systems, support for the multiprocess model ingoogle's chromeweb browser, and zombie and orphan processes in unix.·
n chapter 4, threads, supplies expanded coverage ofparallelism andamdahl's law. it also provides a new section on implicitthreading,including openmp and apple's grand central dispatch.·
n chapter 5, process synchronization (previouslychapter 6), adds a newsection on mutex locks as well as coverage ofsynchronization usingopenmp, as well as functional languages.·
n chapter 6, cpu scheduling (previouslychapter 5), contains new coverageof the linux cfs scheduler andwindows user-mode scheduling.coverageof real-time scheduling algorithms has also been integrated intothischapter.·
n chapter 7:deadlocks ,sections7.1 through 7.3 may be covered quickly for students already familiar withdeadlocks. the bankers algorithm makes an excellent chapter 7, deadlocks.
overview.process management.chapters 3 through 7 describe the process concept and concurrency as the heartof modern operating systems. a process is the unit of work in a system. such asystem consists of a collection of concurrently executing processes, some ofwhich are operating-system processes (those that execute system code) and therest of which are user processes (those that execute user code). these chapterscover methods for process scheduling, interprocess communication, processsynchronization, and deadlock handling. also included is a discussion ofthreads, as well as an examination of issues related to multicore systems andparallel programming.
part 3: memory management |
n chapter 8, main memory, includes new coverage ofswapping on mobilesystems and intel 32- and 64-bit architectures. a new sectiondiscussesarm architecture.·
n chapter 9, virtual memory, updates kernel memorymanagement toinclude the linux slub and slob memory allocators.
·.memory management. chapters 8 and 9 deal with the managementof main memory during the execution of a process. to improve both the utilizationof the cpu and thespeed of its response to its users, the computer must keep several processes inmemory. there are many different memory-management schemes, reflecting variousapproaches to memory management, and the effectiveness of a particular algorithmdepends on the situation.
part 4: storage management |
n chapter 10: mass-storage structure ,sections 10.1, 10.2, and10.4 may be covered quickly depending upon students' background. thedisk scheduling algorithms (section 10.4) make nice programmingexercises. adds cover-age of solid-state disks.·
n chapter 11, file-system interface (previouslychapter 10), is updatedwith information about current technologies.·
n chapter 12, file-system implementation (previouslychapter 11), isupdated with coverage of current technologies.·
n chapter 13, i/o, updates technologies andperformance numbers, expandscoverage of synchronous/asynchronous andblocking/nonblocking i/o,and adds a section on vectored i/o.·
·overview.storage management. chapters 10 through 13describe how mass storage, the file system, and i/o are handled in a modern computer system. thefile system provides the mechanism for on-line storage of and access to bothdata and programs. we describe the classic internal algorithms and structuresof storage management and provide a firm practical understanding of thealgorithms used their properties, advantages, and disadvantages. since the i/o devices that attach to acomputer vary widely, the operating system needs to provide a wide range offunctionality to applications to allow them to control all aspects of thesedevices. we discuss system i/o in depth, including i/o system design, interfaces, and internalsystem structures and functions. in many ways, i/o devices are the slowest major components ofthe computer. because they represent a performance bottleneck, we also examineperformance issues associated with i/o devices.
part 5: protection and security |
n chapter 14 protection,we recommend covering thischapter in its entirety in an advanced operating systems class.
n chapter 15, security, has a revised cryptographysection with modernnotation and an improved explanation of various encryptionmethods andtheir uses. the chapter also includes new coverage ofwindows 7security.·
··overview.protection and security. chapters 14 and 15 discussthe mechanisms necessary for the protection and security of computer systems.the processes in an operating system must be protected from one another's activities,and to provide such protection, we must ensure that only processes that havegained proper authorization from the operating system can operate on the files,memory, cpu, andother resources of the system. protection is a mechanism for controlling theaccess of programs, processes, or users to computer-system resources. thismechanism must provide a means of specifying the controls to be imposed, aswell as a means of enforcement. security protects the integrity of theinformation stored in the system (both data and code), as well as the physicalresources of the system, from unauthorized access, malicious destruction oralteration, and accidental introduction of inconsistency.·
part 6: case studies |
n chapter20, the linux system
n appendix a:bsd unix
: the machsystem
n
overview.case studies. chapters 20 through 22 in the text, alongwith appendices a and b (which are available on (http://www.os-book.com),present detailed case studies of real operating systems, including linux,windows 7,freebsd, and mach. coverage of both linux and windows 7 are presentedthroughout this text; however, the case studies provide much more detail. it isespecially interesting to compare and contrast the design of these two verydifferent systems.
author’s signature shuhua zhu examiner’s signature_____________
date 01/03/2015 date____________________
(dd/mm/yy) (dd/mm/yy)
i. thisform should be completed after discussionbetween the teaching and research section staff of the department concerned,and then confirmed and sealed by the corresponding college. regarding anyspecialized compulsory courses and specialized optional courses, which are notattached to any specific teaching and research section, or are lectured by oneteacher alone, discussion should be organized by the department, andconfirmation signed and sealed by the college. in the case of common optionalcourses, syllabuses should first be drawn up by the lecturer in charge, thendemonstrated and confirmed by specialists selected by the academic affairs department(aad) of the university, and finally approved and signed by the director incharge.
ii. thecontents of the syllabus should be consistent with undergraduate program ofyear 2006 students.
iii. “course type” refers to compulsoryspecialized optional or common optional course.
iv. “” refers tomainland student or non-mainland student.
v. “majorsapplicable to” refers to all the major titles that could be applied to acertain syllabus. “public compulsory course” should be marked as “all majors ofthe university”.
vi. “course offered by” refers to college,department and teaching and research section, or simply college and departmentif the course has no teaching and research section.
vii. “total course hours” are counted as 18hours per i credit for one course.
viii. “ contentsand requirements”. name of practicing/internship to be noted. for detailedinformation, see “laboratory syllabus” or “internship syllabus”.
ix. “textbooksand references” refers to the main textbooks used. instructors should selecttextbooks of high quality, or published within 3 years of the current academicyear; or those recommended by specified research fields. if the instructorschoose self-edited textbooks/ references, they must document the titles of thetextbooks or references and state the reasons for their choice.
x. “gradingsystem and evaluation methods”. grading system refers to the percentageallocation of final scores, with assignments, quizzes and attendance mark etc notexceeding 40% of the total score; evaluation methods refers to the form of theexamination, e.g. “open-book”, “closed-book” or “thesis writing” and so on.
xi. “main points of teaching contents”.instructors should fill in the objectives and requirements, key points, classhour allocation of each chapter, as well as the main contents of each chapter.