Operating System - Distributed Operating Systems - Lecture Slides, Slides of Computer Science

These are the Lecture Slides of Distributed Operating Systems which includes Neumann Bottleneck, Networked Information, Memory Hierarchy, Evidence, Latency, Communication, Intelligent Service, Communication Latency, Routing Path etc.Key important points are: Operating System, Distributed, Case Study, Transparent, Experience, Object Abstraction, Efficient and Reliable, Object Replication, History, National Technical

Typology: Slides

2012/2013

Uploaded on 03/27/2013

ekana
ekana 🇮🇳

4

(44)

370 documents

1 / 15

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Case Study: The E1 Distributed
Operating System
Docsity.com
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff

Partial preview of the text

Download Operating System - Distributed Operating Systems - Lecture Slides and more Slides Computer Science in PDF only on Docsity!

Case Study: The E1 Distributed

Operating System

What is the E1 Operating System?

  • A distributed operating system with a single- system image
  • A transparent user experience based on distributed object abstraction
  • Efficient and reliable due to object replication

Goals of E

  • Provide a convenient interface for users and software developers
  • Maximize efficiency by minimizing the influence of remote communication bottlenecks
  • Ensure reliability by providing redundant storage and execution, as well as fault recovery.

Features of E

  • Transparent Access, based on distributed object abstraction

Implements Single System Image paradigm

  • Distributed system looks like a centralized one
  • Allows developers to ignore the physical layout of resources and focus on functionality Based on Distributed Object concept

Features of E

  • Component Model Support Prefabricated, reusable components make software deployment easier The component model specifies the environment in which components operate, including: - Method invocation mechanism - Naming service - Garbage collection Extending the component model across the network provides a convenient environment for distributed application development

Structure of E1: Microkernel

Architecture

  • Microkernel architecture moves vital system- wide processes to a user level

Microkernel operates in a single node (user's machine, etc) Handles operations such as Address Spaces, Threads, Interrupt Dispatching Prevents one massive kernel from handling all system processes over the network

Structure of E

  • System consists of interacting modules located in different network nodes

Replication objects store synchronized state data in one or more nodes on the network Replicating data over the network provides error- handling and recovery Semantics object implements the functionality of the replicated object, so that it can run independent from the object communicating with the network

Structure of E1: Distributed

Objects and Replication

No

How to Use E

  • E1 exists as a prototype but no applications are available yet
  • Distributed objects (programs) can be written in C++ as long as they conform to the documented component model
  • Interface Definition Language and Replication Strategies Compiler exist for integrating programs into the operating system

Applications of E

  • Robust distributed system for developing distributed applications
  • Safe and efficient due to object replication for multiple user use
  • Convenient object-oriented development environment