Proceedings of the Fifth Symposium on Operating Systems Principles - SOSP '75 1975
DOI: 10.1145/800213.806531
|View full text |Cite
|
Sign up to set email alerts
|

Policy/mechanism separation in Hydra

Abstract: The extent to which resource allocation policies are entrusted to user-level software determines in large part the degree of flexibility present in an operating system. In Hydra the determination to separate mechanism and policy is established as a basic design principle and is implemented by the construction of a kernel composed (almost) entirely of mechanisms. This paper presents three such mechanisms (scheduling, paging, protection) and examines how external policies which manipulate them may be constructed… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
41
0

Year Published

1990
1990
2018
2018

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 85 publications
(41 citation statements)
references
References 0 publications
0
41
0
Order By: Relevance
“…The principle of "separating policy from mechanism" [11] applies the term mechanism to the invariant parts and policy to the variant parts. When we maximize the invariant parts we can then build immutable infrastructure that is independent of the policy approach, and define a Universal Policy Model (UPM) to operate on this infrastructure and to describe and interchange between different policy-and application-domains.…”
Section: A This Workmentioning
confidence: 99%
See 2 more Smart Citations
“…The principle of "separating policy from mechanism" [11] applies the term mechanism to the invariant parts and policy to the variant parts. When we maximize the invariant parts we can then build immutable infrastructure that is independent of the policy approach, and define a Universal Policy Model (UPM) to operate on this infrastructure and to describe and interchange between different policy-and application-domains.…”
Section: A This Workmentioning
confidence: 99%
“…Here, the dynamic features are policy, role, and control. In the mid 1970's operating systems began using the term policy as an artifact of control [11], where users could influence kernel-space decisions without requiring an expensive kernel to user space switch. In [18] the authors separate static and dynamic policies for memory allocation, for static memory allocated at scheduling time with dynamic memory changing with the process.…”
Section: B Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…At the same time these successful classic models embody intuitions and principles that are likely to be vital to a comprehensive solution. The premise of sharply separating P-and E-layers builds on the much practised policy/mechanism separation principle first articulated in HYDRA [26]. P-layer specifications express a policy that is ideal in the sense that it ignores issues such as distributed authorization state, network latency, caching, and requirements for off-line use.…”
Section: Introductionmentioning
confidence: 99%
“…Such mechanisms expand the UNIX security model and are implemented in several popular operating systems, such as Solaris and Windows NT [9]. The Hydra capability based operating system [16] separated its access control mechanisms from the definition of its security policy. Follow up operating system such as KeyKOS [11] and EROS [19] divide a secure system into compartments.…”
Section: Related Workmentioning
confidence: 99%