Resource Management - Operating Systems Group

More documents

Recommendations

Info

■ untyped memory in seL4 ■ all physical memory unused after TU Dresden MOS: Resource Management SOLUTION bootstrap is represented by untyped memory capabilities ■ can be granted, split or retyped ■ restricted to powers of 2 (see flexpages) ■ initial resource manager gets all (see σ0) ■ user code decides how to use them 6
TU Dresden MOS: Resource Management SOLUTION ■ application retype UM to kernel objects ■ TCB, endpoint, CNode, VNode, frame, interrupt ■ all kernel bookkeeping for the object uses the underlying physical memory ■ no implicit memory allocation by the kernel ■ retyping and splitting is remembered in capability derivation tree ■ revoking recursively destroys all derived capabilities and kernel objects 7
Page 1 and 2: Faculty of Computer Science Institu
Page 3 and 4: KERNEL RESOURCES TU Dresden MOS: Re
Page 5: TU Dresden MOS: Resource Management
Page 9 and 10: ARCHITECTURES TU Dresden MOS: Resou
Page 11 and 12: 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 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 43 and 44: Manager Service mag TU Dresden MOS:
Page 45 and 46: Factory S S mag fb-drv moe Memory T
Page 49: ■ kernel resource management TU D

Resource Management - Operating Systems Group

Create successful ePaper yourself

Delete template?

Save as template?