Resource Management - Operating Systems Group
Resource Management - Operating Systems Group Resource Management - Operating Systems Group
CONSEQUENCES ■ each application can use its own library OS ■ library OS’es cannot trust each other ■ no central management for global resources ■ think of a file system ■ kernel manages disk ownership with block granularity ■ each library OS comes with its own filesystem implementation ■ one partition per application? TU Dresden MOS: Resource Management 14
TU Dresden MOS: Resource Management SHARING ■ invariants in shared resources must be maintained ■ four mechanisms provided by the exokernel ■ software regions for sub-page memory protection, allows to share state ■ capabilities for access control ■ critical sections ■ wakeup predicates: code downloaded into the kernel for arbitrary checks 15
- Page 1 and 2: Faculty of Computer Science Institu
- Page 3 and 4: KERNEL RESOURCES TU Dresden MOS: Re
- Page 5 and 6: TU Dresden MOS: Resource Management
- Page 7 and 8: TU Dresden MOS: Resource Management
- Page 9 and 10: ARCHITECTURES TU Dresden MOS: Resou
- Page 11 and 12: TU Dresden MOS: Resource Management
- Page 13: TU Dresden MOS: Resource Management
- Page 17 and 18: TU Dresden MOS: Resource Management
- Page 19 and 20: EXAMPLES TU Dresden MOS: Resource M
- Page 21 and 22: wget lwip Ankh TU Dresden MOS: Reso
- Page 23 and 24: L4Re VFS Filesystem Windhoek TU Dre
- Page 25 and 26: L4Re VFS Filesystem Windhoek TU Dre
- Page 27 and 28: Terminal DOpE mag TU Dresden MOS: R
- Page 29 and 30: RESOURCE ACCESS TU Dresden MOS: Res
- Page 31 and 32: GOOGLE CHROME TU Dresden MOS: Resou
- Page 33 and 34: TU Dresden MOS: Resource Management
- Page 35 and 36: Task A Capability Table TU Dresden
- Page 37 and 38: CAP TRANSFER Task A Task B X TU Dre
- Page 39 and 40: CAP TRANSFER Task A Task B X 1 2 3
- Page 41 and 42: TU Dresden MOS: Resource Management
- Page 43 and 44: Manager Service mag TU Dresden MOS:
- Page 45 and 46: Factory S S mag fb-drv moe Memory T
- Page 47 and 48: TU Dresden MOS: Resource Management
- Page 49: ■ kernel resource management TU D
TU Dresden MOS: <strong>Resource</strong> <strong>Management</strong><br />
SHARING<br />
■ invariants in shared resources must be<br />
maintained<br />
■ four mechanisms provided by the exokernel<br />
■ software regions for sub-page memory<br />
protection, allows to share state<br />
■ capabilities for access control<br />
■ critical sections<br />
■ wakeup predicates: code downloaded into<br />
the kernel for arbitrary checks<br />
15
Change language