User-level Andreas Zoor & scheduling Nikolai Nagibin Whats - - PowerPoint PPT Presentation

user level
SMART_READER_LITE
LIVE PREVIEW

User-level Andreas Zoor & scheduling Nikolai Nagibin Whats - - PowerPoint PPT Presentation

13.02.2014 User-level Andreas Zoor & scheduling Nikolai Nagibin Whats User-level scheduling Export scheduling policies form the kernel in the User- level Based on the idea of microkernel based operating systems


slide-1
SLIDE 1

13.02.2014

User-level scheduling

Andreas Zoor & Nikolai Nagibin

slide-2
SLIDE 2

What’s User-level scheduling

  • ❖ Export scheduling policies form the kernel in the User-

level

❖ Based on the idea of microkernel based operating

systems

slide-3
SLIDE 3

Microkernel based operating systems

❖ Minimize the kernel part of the operating system ❖ For more modularity, flexibility and small ”Trusted

Computing Base“

❖ Just include scheduling mechanism, address calculation

and a messaging service (IPC)

❖ All resource-management policies have to be

implemented at user-level as server applications

slide-4
SLIDE 4

Idea of user-level scheduling

slide-5
SLIDE 5

Why using user-level scheduling ?

slide-6
SLIDE 6

CPU Inheritance Scheduling

❖ Traditionally scheduling is on low

level: by kernel scheduler or by user-level thread packages

❖ New approach: higher-level

threads donate CPU+resources to

  • thers

❖ "Inheritance": ability to donate and

request (virtual) CPU time between threads

❖ Client threads can act as scheduler

threads for others

❖ Root scheduler owns real CPU time

slide-7
SLIDE 7

CPU Usage Accounting

❖ Statistical accounting ❖ Time stamp-based accounting ❖ Directly implement by root

schedulers

❖ Virtual time information for

clients of other schedulers

slide-8
SLIDE 8

Priority inversion

slide-9
SLIDE 9

Overhead

❖ Is it efficient enough in

practice?

❖ Two additional sources of

  • verhead

❖ Caused by dispatcher ❖ and add. context switches

slide-10
SLIDE 10

View: Exokernel

slide-11
SLIDE 11

Conclusion

❖ CPU inheritance scheduling has low overhead ❖ All threads in one address space ❖ A threads has access to memory of all applications ❖ Is it possible to use the concept of CPU inheritance

scheduling for more address spaces?

slide-12
SLIDE 12

That’s all Folks

❖ Thanks for your Attention!