HYDRA The part of a Multiprocessor Operating System by Wulf and so forth. Presentation By Alex Kachurin and Mohamed Saa

1600 days ago, 687 views
PowerPoint PPT Presentation

Presentation Transcript

Slide 1

HYDRA – The bit of a Multiprocessor Operating System by Wulf and so forth. (Presentation By Alex Kachurin and Mohamed Saad Laassel) Introduction To Hydra Design Philosophy Overview Of The Hydra Environment The Protection Mechanism Path Names And Walk Right Systems And Subsystems An Example (Bibliography System) Conclusion References

Slide 2

Introduction to Hydra Designed in mid 70's, Carnegie-Melon University Not an OS independent from anyone else, but instead a piece base for a gathering of OS'es. (e.g Linux portion versus Debian Linux) Runs on C.mmp, a multiprocessor built at Carnegie-Melon University (up to 16 processors, up to 32 MB of memory, crossbar switch engineering versus transport engineering) The objective is " to misuse and investigate the potential innate in a multiprocessor PC framework". Give a domain to compelling use of the equipment assets To encourage the development of such environment

Slide 3

Separation of component and arrangement (High level strategies, for example, planning and security versus low level instruments, for example, message dispatching) Multiprocessor environment. Numerous examples of the frameworks coincide together Integration of the plan with usage procedure (Structured programming, particular approach) Rejection of strict various leveled layering. (Famous since Dijkstra's THE framework, yet confines adaptability) Protection Reliability (16 processors, repetition, mistake recuperation) Design Philosophy

Slide 4

Design Philosophy Need to choose what has a place with the portion and what does not. Key standards: A portion is to give offices to building a working framework. A working framework characterizes a "abstract machine" by giving offices, or assets, which are more advantageous than those gave by the uncovered equipment. A working framework assigns (equipment) assets so as to most viably use them. Cases of assets are called "objects". Objects have a place with a few unmistakable "sorts" (question based framework) Reference number and rubbish accumulation

Slide 5

Overview of Hydra Environment Key terms: Procedures, Local Namespaces (LNS), Processes and Capabilities Hydra techniques bolster security offices through layouts (formal parameters list) Hydra systems are reenterant and possibly recursive LNS is a record of execution environment at the season of summon LNS is changing and gets created every time a methodology is conjured, in light of capacities LNS gets deleted when a strategy completes Capability is a reference to a protest alongside a gathering of get to rights to this protest. Abilities are controlled by the portion so they can't be manufactured. Abilities are put away in C-records

Slide 6

Overview of Hydra Environment Hydra Process is the littlest substance that can be planned for execution Processes are spoken to as heaps of LNS, speaking to the aggregate condition of a solitary successive assignment. Synchronization primitives (Semaphores, Locks, Mutexes)

Slide 7

The Protection Mechanism Protection versus Security: assurance is an instrument, security is an arrangement Protection is strategy based instead of process-based Procedure itself is a question so it has abilities list (guest autonomous capacities). Guest free abilities are acquired from the called procedure. Systems have formats (formal parameters list). Get to privileges of the genuine parameters are checked at the season of summon. Callee (the called methodology) has more opportunity than the calling strategy. Portion gives CALL and RETURN instruments to instantiate a method or come back to calling technique.

Slide 8

The Protection Mechanism Hydra Access Rights: Generic rights, 16-bit, sort free. Auxillary rights, 8-bit, sort subordinate.

Slide 9

Summary of Hydra's key standards: PROCESS The fundamental unit of booking and execution. Strategy The static portrayal of an executable methodology LOCAL NAME SPACE (LNS) The dynamic representation of an executing technique. SEMAPHORE A synchronization primitive. PORT A message transmission and gathering office. Gadget A physical I/O gadget. Approach A module that can settle on abnormal state booking arrangement choices. Information A question with an information part as it were. Widespread An essential question with both a C-list and datapart. Sort The delegate for all objects of a given sort CAPABILITY A reference to a protest + question's get to rights

Slide 10

Refresher… An ability comprises of a reference to a protest together with a gathering of "access rights" to that protest. Ownership of an ability is taken as proof that the holder may get to the question in the routes, and in just the courses, depicted by the capacity. Abilities themselves are controlled just by the portion; henceforth it is difficult to "forge" a capacity. A LNS (neighborhood name space) is the record of the execution environment of a system when that methodology is conjured (called). There is an interesting LNS for every conjuring, which vanishes after the methodology ends. The LNS characterizes the totality of abilities accessible to a methodology amid the execution coming about because of a specific conjuring.

Slide 11

Path Names and the Walk Right The walk primitive is a one-level intimidation which, given an ability and a nonnegative whole number, delivers the capacity which involves the predetermined position in the ability part of the question named by the parameter capacity. The walk primitive, similar to all portion primitives, is a get to right ensured by the "kernel rights" bits in an ability. Due to the walk primitive, the earth of a technique does not comprise of the articles named by abilities in its LNS alone. It is the conclusion of the arrangement of articles reachable along a way (beginning in the LNS) with the end goal that each ability along the way (aside from conceivably the last) give the walk right.

Slide 12

Path Names… (Contd) All of the piece primitives acknowledge way names as parameters and the walk right is checked at every progression along the way. The utilization of way names and walk rights result in a huge lessening in the quantity of abilities required in a LNS. Much more essential, in any case, is that the walk right (or rather the absence of it) is utilized to anticipate access to the representation of a protest.

Slide 13

Systems and Subsystems In the HYDRA setting a client domain comprises of a gathering of assets (articles) of different sorts and strategies which work on them. The earth in which one client works might possibly be the same as that for another client, it might be very surprising, or may in part cover.

Slide 14

New question sorts First, a case of a protest might be made by summoning a bit primitive make and going to it an ability referencing the agent of kind of question one wishes to make. At that point, conjuring make with a capacity referencing the recognized question named TYPE will make the delegate of another sort class. Resulting approaches make passing abilities referencing this new sort agent will make cases of the new class of articles.

Slide 15

Bibliography illustration We display a case which shows the force of the security system gave to us by abilities. Consider the instance of an examination laborer who, wishes to stay up with the latest with the writing in his field. This scientist has composed a few projects to keep up a clarified list of sources The projects allow him to overhaul the reference index either by embeddings new passages or changing existing ones; he may likewise print the book index altogether, or specifically on any of a few criteria; he may likewise wish to totally delete a whole list of sources infrequently.

Slide 16

Bibliography illustration (Contd) Later on, the specialist concludes that he might want to impart his projects and his catalogs to his partners. The associates might have the capacity to make new lists of sources, or add new passages to the analyst's own. He is concerned, be that as it may, around a few parts of the insurance of both his projects and information: 1. Nobody, with the exception of himself, ought to have the capacity to delete his reference indices. 2. He buckled down on his reference indices, and he dislike everyone to duplicate and change them.

Slide 17

The Implementation in HYDRA A reference index is another sort of virtual asset. Along these lines, we would make another protest sort; call it BIBLIO. We make new techniques which are material to book reference objects, for instance: U( β ) Update P( β ) Print PWOA( β ) Print Without Annotations E( β ) Erase In each of these, β must be a capacity which references a list of sources protest.

Slide 19

Diagram clarification User #1 may get to the majority of the techniques U, P, PWOA, and E. He may likewise get to book reference objects B1 and B2. He may play out any of the operations U, P, PWOA, and E on B1, however he may just perform U and PWOA on B2. Client #2 may likewise get to the majority of the methods and, what's more, may get to three book index objects: B2, B3, and B4. He may just perform PWOA on B2, however may perform U, P, or E on B3 and B4. Accept that user# 2, did not have admittance to system E, the privilege to perform E on B3 and B4 is pointless, since he doesn't have a reference to ability E.

Slide 20

Conclusion The HYDRA O.S, was outlined on account of one extreme objective: to be the "kernel" base for an accumulation of working frameworks intended to abuse and investigate the capability of a multiprocessor PC framework. This objective was acknowledged through the presentation of a summed up thought of "resource," both physical and virtual, called a "object." Mechanisms are introduced for managing objects, including the making of new sorts, detail of new operations appropriate to a given sort, sharing, and assurance of any reference to a given protest against inappropriate appli