Lesson 2b (SPIN) Flashcards

1
Q

Key points of Hydra

A

Kernel mechanism for resource allocation. Capability based resource access. Resource manager as coarse-grain objects to reduce border crossing overhead

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What was the disadvantage of MACH

A

It focused on portability which made it slow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

In SPIN where were extensions located

A

They were colocated with the kernel

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How was modularity enforced in SPIN

A

Using the compiler and a strongly typed language

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What language was SPIN written

A

Modula-3

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Which of the three OS structures is SPIN similar to?

A

DOS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

How did SPIN avoid security issues

A

Using logical protection domains

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the benefits that modula-3 provided

A

Safety+Encapsulation. type safety, auto storage management. Objects, threads, exception, generic interfaces

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How was fine grain protection provided

A

via capabilites

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are capabilities essentialy

A

pointers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How are Modula-3 pointers safe

A

They are type specific. This allowed for protection the os takes advantage of

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

List the spin mechanisms for protection domains

A

Create, Resolve, combine

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Create

A

init with object file contents and export names

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

resolve

A

names between source and target domain, Once resolved resource sharing at memory speed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

combine

A

to create an aggregate domain

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How are core services included

A

provided components implement specified interfaces

17
Q

What makes the extensions flexible

A

co-location systems extensions are dynamically linked

18
Q

What language in SPIN can applications be written in?

A

Any language

19
Q

Perfomance

A

It performed better than MACH comparable to Micro

20
Q

How does the kernel know where to send message and interupts

A

It has an event dispatcher and service can create handlers

21
Q

How are services siloed in memory

A

they are not, all services share the same address space

22
Q

How are system services built

A

As logical extensions

23
Q

What is the limit of an extensions

A

None really. The extension can be an entire OS

24
Q

How are events in the dispatcher ordered

A

Order of events isn’t guaranteed

25
What are the relationships possible with handlres
many to one, one to one, one to many
26
How many border crossings are needed to reach a service
One border crossing is needed to reach the services and another is needed for the results.
27
Where is the memory management
It is added as a service
28
How does the kernel talk to the memory manager
SPIN defines the interface
29
How would a page fault get routed
A handler would be in place for the kernel trap that the kernel would dispatch to the memory management service.
30
Where is the cpu scheduler located
As a service. It is not built in.
31
What is Stand
Strand is a unit of scheduling set by the global scheduler which interacts with application thread package.
32
How is cpu time scheduled
Services given thread time by SPIN can schedule cpu time how they like