Operating System - Case Study - MINIX Notes, Study notes of Operating Systems

In this document topics covered which are Case Study : Minix, The Internal Structure of MINIX 3, Working of Kernel Layer, Assembly Language in Minix, Overview of System Task , The Internal Structure of MINIX 3.

Typology: Study notes

2010/2011

Uploaded on 09/01/2011

visir66
visir66 🇮🇳

4.4

(74)

97 documents

1 / 68

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Case Study : Minix
Basics of OS is already discussed:
Processor Management
Memory Management
File Management
Disk Management
Lets apply all this with Minix.
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36
pf37
pf38
pf39
pf3a
pf3b
pf3c
pf3d
pf3e
pf3f
pf40
pf41
pf42
pf43
pf44

Partial preview of the text

Download Operating System - Case Study - MINIX Notes and more Study notes Operating Systems in PDF only on Docsity!

Case Study : Minix

  • (^) Basics of OS is already discussed:
    • (^) Processor Management
    • (^) Memory Management
    • (^) File Management
    • (^) Disk Management
  • (^) Lets apply all this with Minix.

The Internal Structure of MINIX 3

  • (^) MINIX 3 is structured in four layers, with each layer performing a well-defined function.

Assembly Language in Minix

  • (^) Minix is primarily written in C.
    • (^) But some assembly language code is also there.

Assembly Language in Minix

  • (^) The assembly language parts deal with
    • (^) interrupt handling,
    • (^) the low-level mechanics of managing context switches between processes (saving and restoring registers and the like),
    • (^) and low-level parts of manipulating the MMU hardware.

Limitations of User Layer

  • (^) Layers are divided into 2 groups;
    • (^) Kernel Layer
    • (^) User Process, Server Process and Device Drivers
  • (^) Layers other than kernel is limited to user mode instructions, and each is scheduled to run by the kernel.
  • (^) None of them can access I/O ports directly. Furthermore, none of them can access memory outside the segments allotted to it.

File System Server

  • (^) The file system (FS) carries out all the file system calls, such as - (^) read, - (^) mount, - (^) and chdir.

Kernel calls

  • (^) Kernel calls are low-level functions provided by the system task to allow the drivers and servers to do their work.
  • (^) Reading a hardware I/O port is a typical kernel call.

Posix Calls

  • (^) In contrast, the POSIX system calls such as read, fork, and unlink are high-level calls defined by the POSIX standard, and are available to user programs in layer 4.
  • (^) User programs contain many POSIX calls but no kernel calls.

Overview of System Task (1)

The message types accepted by the system task.

Overview of System Task (2)

“Any” means any system process; user processes cannot call the system task directly

Information server (IS)

  • (^) The information server (IS) handles jobs such as providing debugging and status information about drivers and servers.
  • The Internal Structure of MINIX
  • The Internal Structure of MINIX
  • The Internal Structure of MINIX
  • The Internal Structure of MINIX
  • The Internal Structure of MINIX