DOCSLIB.ORG

IBM Research Report Service Oriented File Systems Eric Van

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM Research Report Service Oriented File Systems Eric Van RC24788 (W0904-091) April 21, 2009 Computer Science IBM Research Report Service Oriented File Systems Eric Van Hensbergen, Noah Evans IBM Research Division Austin Research Laboratory 11501 Burnet Road Austin, TX 78758 Phillip Stanley-Marbell IBM Research GmbH Zurich Research Laboratory 8803 Rüschlikon Switzerland Research Division Almaden - Austin - Beijing - Cambridge - Haifa - India - T. J. Watson - Tokyo - Zurich Service Oriented File Systems Eric Van Hensbergen Noah Evans Phillip Stanley-Marbell IBM Research Austin IBM Research Austin IBM Research Zurich [email protected] [email protected] [email protected] Abstract RESTful applications differ from their RPC counter- parts in relying principally on resource identifiers versus Service Oriented Architectures (SOAs) are a loose command methods. In web environments, this results in coupling of network services providing methods for sys- operational semantics being encoded as part of the URL tems development and integration. Interoperability be- of HTTP requests, and relying on HTTP methods (GET, tween different systems and programming languages is PUT, POST, DELETE) as the sole methods. This al- provided via communication protocols and well defined lows service components to access and navigate service messages. The recent development trend has been to infrastructures without requiring complete knowledge of favor RESTful approaches for these interfaces, which the resource capabilities or data structures. Existing run- encode relevant context and semantic metadata into the times each use their own language-specific bindings for URL of an HTTP GET or PUT operation. accessing and addressing these service methods. We observe that this approach is essentially a sim- plified web-instantiation of synthetic file system based It is our belief that it is the responsibility of systems service interfaces, such as those originally pioneered by software to provide a unified language- and network- UNIX and later the Plan 9 and Inferno operating sys- neutral interface to its users. As such, we believe that tems. In this paper we advocate the collapse of the the operating system should provide facilities for ad- software stack by abstracting the underlying transport dressing and interaction of SOA interfaces. We feel that and naming details, and accessing RESTful services via enabling interaction via system-provided interfaces en- standard file system interfaces. We explore the research ables a new degree of composability and flexibility in challenges and opportunities presented by taking such much the same way as pipes unlocked tool-based ap- an approach to building comprehensive dynamic dis- proaches in UNIX [10]. tributed systems appropriate for large scale cloud com- Our proposal is motivated by our observation that the puting. semantically significant URL path component of REST- ful operations is similar in many ways to synthetic file 1 Introduction system environments such as UNIX’s /proc, or those used in the Plan 9 or Inferno operating systems (Fig- Service-oriented architectures (SOAs) are networked ure 1). The introduction of the File Systems in User software infrastructures in which resources are made Space (FUSE) and 9P file systems into the mainline available through a transactional interface [19]. They Linux kernel has further enabled the use of such file typically comprise collections of reusable application system interfaces as an applications component in main- modules, each of which expose standardized interfaces. stream environments. We propose the use of such mech- The use of well-defined protocols and message for- anisms to allow RESTful interfaces to be managed, or- mats to communicate between these services decou- ganized, and interconnected by the operating system in- ples application implementations from one another, pro- stead of purely by an SOA runtime. It is our belief viding greater degrees of flexibility and composability. that using synthetic file systems to establish operating The popularity of the web has lead to many SOA run- system based uniform interface abstractions and appli- times adopting HTTP encapsulated protocols such as cation orchestration will further enable the benefits of SOAP [12]. SOAs while also enabling a seamless distributed com- The emergence of Web 2.0 and cloud computing has puting environment across platforms to enable large- extended the SOA development paradigm from busi- scale “cloud” environments. ness process services to complete computing environ- ments, involving everything from the customer-facing interfaces to the back-end database. These new classes 2 Background of application have evolved from client-server based tra- UNIX pioneered the concept of treating devices as files, ditional RPC exemplified by SOAP, to representational providing a uniform interface to system hardware. In the state transfer (REST) [6] mechanisms as their common 8th edition, this methodology was taken further through communication architecture. the introduction of the /proc synthetic file system to syscontext/ clone http://y.com/sys/spucontext mem 0/ [An HTTP transaction (e.g., GET) to achieve resource run 1/ instance creation, for instance syscontext . This returns mbox ... an identifier pointing to the new instance. ] wbox n/ http://y.com/sys/1/mem ibox ctl [URI captures instantiated identifier and resource to be data accessed. Payload of HTTP request contains data for this interaction. ] ... (a). An example "Old Unix (b). A typical dynamic (c). An example RESTful interface to a system service style" virtual filesystem, fileserver in Plan 9/Inferno; exposed over HTTP. SYSFS; data exchange via file abstractions are used files, but control and resource for resource instance instance creation via ioctl() creation ( clone ), control and create() system calls. (ctl ) and data ( data ). Figure 1: Illustration of a service–oriented file system interface manage user processes [8]. Synthetic file systems are files and read/write the necessary data to the proper lo- comprised of elements with no physical storage, i.e., the cation. files represented are not present on any disk. Instead, op- In addition to providing language portability, syn- erations on the file communicate directly with the kernel thetic file systems provide data portability as well. They sub-system or application providing the service. This can act as intermediaries between the physical data and methodology has persisted over the evolution of UNIX the presentation, interpreting data in the most appropri- and UNIX-like systems, and the Linux kernel now sup- ate way for a given application. Again this moves the ports several synthetic file systems representing devices, responsibility for ensuring data from the user to system, process control, as well as access to system services and removing much of the burden of data conversion from data structures. the user. For example files of one type, say xml data, The Plan 9 [14] and Inferno [15] operating systems can be presented as yaml and vice versa. Further exam- took the file system metaphor further, using file opera- ples of this process appear in [5]. tions as the simple, well-defined interface to all system Synthetic file systems have the unique property of be- and application services. As such, interfaces to all kernel ing implementable either within the operating system or subsystems, from the networking stack to the graphics in user space, but still providing a single consistent in- frame buffer, are represented within synthetic file sys- terface through the operating system’s file system name tems. User-space applications and services may also ex- space. Using synthetic file systems as interfaces for port their own synthetic file systems, in much the same software implementations decouples software function- way as the kernel interfaces. Common services such as ality from decisions about implementation location, pro- domain name service (DNS), authentication databases, gramming language bindings, or runtime system sup- and window management are all provided as file sys- port. tems. Even end-user applications such as editors and e-mail systems export file system interfaces as a means 3 Approach for data exchange and control. The benefits and details Following Plan 9’s example, we propose the pervasive of this approach are covered in detail elsewhere [16]. use of synthetic file systems as a resource interface ab- The intuition behind the design was based on the straction, and an augmented form of UNIX pipelines to- assumption that any programmer knows how to inter- gether with application of dynamic private name spaces act with files. Every programming language has the to achieve this goal. We believe that by collapsing the in- means of interacting with file systems, and network pro- frastructure of service-oriented architecture stacks back tocols (including HTTP) for remote access of file hier- into the system, we can return the flexibility and ele- archies are readily available. Application frameworks gance of the composable modular approach exemplified implemented as file systems eliminate many of the op- by UNIX. erating system and language portability problems that The presence of service interfaces within the operat- occur when implementers develop new protocols and ing system name space allows for natural naming and interfaces—the responsibility for the interactions occur addressability, freeing services from location-dependent at the systems level, making a new API unnecessary. numeric identifiers such as IP addresses and port num- Programs just navigate a file hierarchy open
Load more

Recommended publications
  • Enhancing the Accuracy of Synthetic File System Benchmarks Salam Farhat Nova Southeastern University, [email protected]
    Nova Southeastern University NSUWorks CEC Theses and Dissertations College of Engineering and Computing 2017 Enhancing the Accuracy of Synthetic File System Benchmarks Salam Farhat Nova Southeastern University, [email protected] This document is a product of extensive research conducted at the Nova Southeastern University College of Engineering and Computing. For more information on research and degree programs at the NSU College of Engineering and Computing, please click here. Follow this and additional works at: https://nsuworks.nova.edu/gscis_etd Part of the Computer Sciences Commons Share Feedback About This Item NSUWorks Citation Salam Farhat. 2017. Enhancing the Accuracy of Synthetic File System Benchmarks. Doctoral dissertation. Nova Southeastern University. Retrieved from NSUWorks, College of Engineering and Computing. (1003) https://nsuworks.nova.edu/gscis_etd/1003. This Dissertation is brought to you by the College of Engineering and Computing at NSUWorks. It has been accepted for inclusion in CEC Theses and Dissertations by an authorized administrator of NSUWorks. For more information, please contact [email protected]. Enhancing the Accuracy of Synthetic File System Benchmarks by Salam Farhat A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor in Philosophy in Computer Science College of Engineering and Computing Nova Southeastern University 2017 We hereby certify that this dissertation, submitted by Salam Farhat, conforms to acceptable standards and is fully adequate in scope and quality to fulfill the dissertation requirements for the degree of Doctor of Philosophy. _____________________________________________ ________________ Gregory E. Simco, Ph.D. Date Chairperson of Dissertation Committee _____________________________________________ ________________ Sumitra Mukherjee, Ph.D. Date Dissertation Committee Member _____________________________________________ ________________ Francisco J.
    [Show full text]
  • Clustering with Openmosix
    Clustering with openMosix Maurizio Davini (Department of Physics and INFN Pisa) Presented by Enrico Mazzoni (INFN Pisa) Introduction • What is openMosix? – Single-System Image – Preemptive Process Migration – The openMosix File System (MFS) • Application Fields • openMosix vs Beowulf • The people behind openMosix • The openMosix GNU project • Fork of openMosix code 12/06/2003 HTASC 2 The openMosix Project MileStones • Born early 80s on PDP-11/70. One full PDP and disk-less PDP, therefore process migration idea. • First implementation on BSD/pdp as MS.c thesis. • VAX 11/780 implementation (different word size, different memory architecture) • Motorola / VME bus implementation as Ph.D. thesis in 1993 for under contract from IDF (Israeli Defence Forces) • 1994 BSDi version • GNU and Linux since 1997 • Contributed dozens of patches to the standard Linux kernel • Split Mosix / openMosix November 2001 • Mosix standard in Linux 2.5? 12/06/2003 HTASC 3 What is openMOSIX • Linux kernel extension (2.4.20) for clustering • Single System Image - like an SMP, for: – No need to modify applications – Adaptive resource management to dynamic load characteristics (CPU intensive, RAM intensive, I/O etc.) – Linear scalability (unlike SMP) 12/06/2003 HTASC 4 A two tier technology 1. Information gathering and dissemination – Support scalable configurations by probabilistic dissemination algorithms – Same overhead for 16 nodes or 2056 nodes 2. Pre-emptive process migration that can migrate any process, anywhere, anytime - transparently – Supervised by adaptive
    [Show full text]
  • Virtfs—A Virtualization Aware File System Pass-Through
    VirtFS—A virtualization aware File System pass-through Venkateswararao Jujjuri Eric Van Hensbergen Anthony Liguori IBM Linux Technology Center IBM Research Austin IBM Linux Technology Center [email protected] [email protected] [email protected] Badari Pulavarty IBM Linux Technology Center [email protected] Abstract operations into block device operations and then again into host file system operations. This paper describes the design and implementation of In addition to performance improvements over a tradi- a paravirtualized file system interface for Linux in the tional virtual block device, exposing guest file system KVM environment. Today’s solution of sharing host activity to the hypervisor provides greater insight to the files on the guest through generic network file systems hypervisor about the workload the guest is running. This like NFS and CIFS suffer from major performance and allows the hypervisor to make more intelligent decisions feature deficiencies as these protocols are not designed with respect to I/O caching and creates new opportuni- or optimized for virtualization. To address the needs of ties for hypervisor-based services like de-duplification. the virtualization paradigm, in this paper we are intro- ducing a new paravirtualized file system called VirtFS. In Section 2 of this paper, we explore more details about This new file system is currently under development and the motivating factors for paravirtualizing the file sys- is being built using QEMU, KVM, VirtIO technologies tem layer. In Section 3, we introduce the VirtFS design and 9P2000.L protocol. including an overview of the 9P protocol, which VirtFS is based on, along with a set of extensions introduced for greater Linux guest compatibility.
    [Show full text]
  • Virtio-Fs a Shared File System for Virtual Machines
    FOSDEM ‘20 virtio-fs A Shared File System for Virtual Machines Stefan Hajnoczi [email protected] 1 FOSDEM ‘20 About me I work in Red Hat’s virtualization team: virtio-fs virtio-blk tracing VIRTIO specification open source internships QEMU Linux https://vmsplice.net/ “stefanha” on IRC 2 FOSDEM ‘20 What is virtio-fs? Share a host directory with the guest ➔ Run container images from host but isolated inside a guest ➔ File System as a Service ➔ Compile on host, test inside guest ➔ Get files into guest at install time ➔ Boot guest from directory on host See KVM Forum talk for “what” and “why”: https://www.youtube.com/watch?v=969sXbNX01U 3 FOSDEM ‘20 How to use virtio-fs “I want to share /var/www with the guest” Not yet widely available in distros, but the proposed libvirt domain XML looks like this: <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs'/> <source dir='/var/www'/> <target dir='website'/> <!-- not treated as a path --> </filesystem> 4 FOSDEM ‘20 How to use virtio-fs (Part 2) Mount the directory inside the guest: guest# mount -t virtiofs website /var/www And away you go! 5 FOSDEM ‘20 Performance (with a grain of salt) Out-of-the-box performance on NVMe. Virtio-fs cache=none, no DAX. Linux 5.5.0-rc4 based virtio-fs-dev branch 6 FOSDEM ‘20 How do remote file systems work? Two ingredients: 1. A transport for communication TCP/IP, USB, RDMA 2. A protocol for file system operations NFS, CIFS, MTP, FTP Protocol Client Server Transport 7 FOSDEM ‘20 virtio-fs as a remote file system Protocol is based on Linux FUSE
    [Show full text]
  • Load Balancing Experiments in Openmosix”, Inter- National Conference on Computers and Their Appli- Cations , Seattle WA, March 2006 0 0 5 4 9
    Machine Learning Approach to Tuning Distributed Operating System Load Balancing Algorithms Dr. J. Michael Meehan Alan Ritter Computer Science Department Computer Science Department Western Washington University Western Washington University Bellingham, Washington, 98225 USA Bellingham, Washington, 98225 USA [email protected] [email protected] Abstract 2.6 Linux kernel openMOSIX patch was in the process of being developed. This work concerns the use of machine learning techniques (genetic algorithms) to optimize load 2.1 Load Balancing in openMosix balancing policies in the openMosix distributed The standard load balancing policy for openMosix operating system. Parameters/alternative algorithms uses a probabilistic, decentralized approach to in the openMosix kernel were dynamically disseminate load balancing information to other altered/selected based on the results of a genetic nodes in the cluster. [4] This allows load information algorithm fitness function. In this fashion optimal to be distributed efficiently while providing excellent parameter settings and algorithms choices were scalability. The major components of the openMosix sought for the loading scenarios used as the test load balancing scheme are the information cases. dissemination and migration kernel daemons. The information dissemination daemon runs on each 1 Introduction node and is responsible for sending and receiving The objective of this work is to discover ways to load messages to/from other nodes. The migration improve the openMosix load balancing algorithm. daemon receives migration requests from other The approach we have taken is to create entries in nodes and, if willing, carries out the migration of the the /proc files which can be used to set parameter process. Thus, the system is sender initiated to values and select alternative algorithms used in the offload excess load.
    [Show full text]
  • HPC with Openmosix
    HPC with openMosix Ninan Sajeeth Philip St. Thomas College Kozhencheri IMSc -Jan 2005 [email protected] Acknowledgements ● This document uses slides and image clippings available on the web and in books on HPC. Credit is due to their original designers! IMSc -Jan 2005 [email protected] Overview ● Mosix to openMosix ● Why openMosix? ● Design Concepts ● Advantages ● Limitations IMSc -Jan 2005 [email protected] The Scenario ● We have MPI and it's pretty cool, then why we need another solution? ● Well, MPI is a specification for cluster communication and is not a solution. ● Two types of bottlenecks exists in HPC - hardware and software (OS) level. IMSc -Jan 2005 [email protected] Hardware limitations for HPC IMSc -Jan 2005 [email protected] The Scenario ● We are approaching the speed and size limits of the electronics ● Major share of possible optimization remains with software part - OS level IMSc -Jan 2005 [email protected] Hardware limitations for HPC IMSc -Jan 2005 [email protected] How Clusters Work? Conventional supe rcomputers achieve their speed using extremely optimized hardware that operates at very high speed. Then, how do the clusters out-perform them? Simple, they cheat. While the supercomputer is optimized in hardware, the cluster is so in software. The cluster breaks down a problem in a special way so that it can distribute all the little pieces to its constituents. That way the overall problem gets solved very efficiently. - A Brief Introduction To Commodity Clustering Ryan Kaulakis IMSc -Jan 2005 [email protected] What is MOSIX? ● MOSIX is a software solution to minimise OS level bottlenecks - originally designed to improve performance of MPI and PVM on cluster systems http://www.mosix.org Not open source Free for personal and academic use IMSc -Jan 2005 [email protected] MOSIX More Technically speaking: ● MOSIX is a Single System Image (SSI) cluster that allows Automated Load Balancing across nodes through preemptive process migrations.
    [Show full text]
  • Introduction Course Outline Why Does This Fail? Lectures Tutorials
    Course Outline • Prerequisites – COMP2011 Data Organisation • Stacks, queues, hash tables, lists, trees, heaps,…. Introduction – COMP2021 Digital Systems Structure • Assembly programming • Mapping of high-level procedural language to assembly COMP3231/9201/3891/9283 language – or the postgraduate equivalent (Extended) Operating Systems – You are expected to be competent Kevin Elphinstone programmers!!!! • We will be using the C programming language – The dominant language for OS implementation. – Need to understand pointers, pointer arithmetic, explicit 2 memory allocation. Why does this fail? Lectures • Common for all courses (3231/3891/9201/9283) void func(int *x, int *y) • Wednesday, 2-4pm { • Thursday, 5-6pm *x = 1; *y = 2; – All lectures are here (EE LG03) – The lecture notes will be available on the course web site } • Available prior to lectures, when possible. void main() – The lecture notes and textbook are NOT a substitute for { attending lectures. int *a, *b; func(a,b); } 3 4 Tutorials Assignments • Assignments form a substantial component of • Start in week 2 your assessment. • A tutorial participation mark will • They are challenging!!!! – Because operating systems are challenging contribute to your final assessment. • We will be using OS/161, – Participation means participation, NOT – an educational operating system attendance. – developed by the Systems Group At Harvard – Comp9201/3891/9283 students excluded – It contains roughly 20,000 lines of code and comments • You will only get participation marks in your enrolled tutorial. 5 6 1 Assignments Assignments • Assignments are in pairs • Don’t under estimate the time needed to do the – Info on how to pair up available soon assignments. • We usually offer advanced versions of the – ProfQuotes: [About the midterm] "We can't keep you working assignments on it all night, it's not OS.“ Ragde, CS341 – Available bonus marks are small compared to amount of • If you start a couple days before they are due, you will be late.
    [Show full text]
  • The Utility Coprocessor: Massively Parallel Computation from the Coffee Shop
    The Utility Coprocessor: Massively Parallel Computation from the Coffee Shop John R. Douceur, Jeremy Elson, Jon Howell, and Jacob R. Lorch Microsoft Research Abstract slow jobs that take several minutes without UCop be- UCop, the “utility coprocessor,” is middleware that come interactive (15–20 seconds) with it. Thanks to makes it cheap and easy to achieve dramatic speedups the recent emergence of utility-computing services like of parallelizable, CPU-bound desktop applications using Amazon EC2 [8] and FlexiScale [45], which rent com- utility computing clusters in the cloud. To make UCop puters by the hour on a moment’s notice, anyone with a performant, we introduced techniques to overcome the credit card and $10 can use UCop to speed up his own low available bandwidth and high latency typical of the parallel applications. networks that separate users’ desktops from a utility One way to describe UCop is that it effectively con- computing service. To make UCop economical and easy verts application software into a scalable cloud service to use, we devised a scheme that hides the heterogene- targeted at exactly one user. This goal entails five re- ity of client configurations, allowing a single cluster to quirements. Configuration transparency means the ser- serve virtually everyone: in our Linux-based prototype, vice matches the user’s application, library, and con- the only requirement is that users and the cluster are us- figuration state. Non-invasive installation means UCop ing the same major kernel version. works with a user’s existing file system and application This paper presents the design, implementation, and configuration.
    [Show full text]
  • Legoos: a Disseminated, Distributed OS for Hardware Resource
    LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation Yizhou Shan, Yutong Huang, Yilun Chen, and Yiying Zhang, Purdue University https://www.usenix.org/conference/osdi18/presentation/shan This paper is included in the Proceedings of the 13th USENIX Symposium on Operating Systems Design and Implementation (OSDI ’18). October 8–10, 2018 • Carlsbad, CA, USA ISBN 978-1-939133-08-3 Open access to the Proceedings of the 13th USENIX Symposium on Operating Systems Design and Implementation is sponsored by USENIX. LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation Yizhou Shan, Yutong Huang, Yilun Chen, Yiying Zhang Purdue University Abstract that can fit into monolithic servers and deploying them in datacenters is a painful and cost-ineffective process that The monolithic server model where a server is the unit often limits the speed of new hardware adoption. of deployment, operation, and failure is meeting its lim- We believe that datacenters should break mono- its in the face of several recent hardware and application lithic servers and organize hardware devices like CPU, trends. To improve resource utilization, elasticity, het- DRAM, and disks as independent, failure-isolated, erogeneity, and failure handling in datacenters, we be- network-attached components, each having its own con- lieve that datacenters should break monolithic servers troller to manage its hardware. This hardware re- into disaggregated, network-attached hardware compo- source disaggregation architecture is enabled by recent nents. Despite the promising benefits of hardware re- advances in network technologies [24, 42, 52, 66, 81, 88] source disaggregation, no existing OSes or software sys- and the trend towards increasing processing power in tems can properly manage it.
    [Show full text]
  • Architectural Review of Load Balancing Single System Image
    Journal of Computer Science 4 (9): 752-761, 2008 ISSN 1549-3636 © 2008 Science Publications Architectural Review of Load Balancing Single System Image Bestoun S. Ahmed, Khairulmizam Samsudin and Abdul Rahman Ramli Department of Computer and Communication Systems Engineering, University Putra Malaysia, 43400 Serdang, Selangor, Malaysia Abstract: Problem statement: With the growing popularity of clustering application combined with apparent usability, the single system image is in the limelight and actively studied as an alternative solution for computational intensive applications as well as the platform for next evolutionary grid computing era. Approach: Existing researches in this field concentrated on various features of Single System Images like file system and memory management. However, an important design consideration for this environment is load allocation and balancing that is usually handled by an automatic process migration daemon. Literature shows that the design concepts and factors that affect the load balancing feature in an SSI system are not clear. Result: This study will review some of the most popular architecture and algorithms used in load balancing single system image. Various implementations from the past to present will be presented while focusing on the factors that affect the performance of such system. Conclusion: The study showed that although there are some successful open source systems, the wide range of implemented systems investigated that research activity should concentrate on the systems that have already been proposed and proved effectiveness to achieve a high quality load balancing system. Key words: Single system image, NOWs (network of workstations), load balancing algorithm, distributed systems, openMosix, MOSIX INTRODUCTION resources transparently irrespective of where they are available[1].The load balancing single system image Cluster of computers has become an efficient clusters dominate research work in this environment.
    [Show full text]
  • SEMINARIS DOCENTS DE CASO 03/04 - 2Q NÚM GRUP: Facultat D´Informàtica De Barcelona - Departament AC - UPC
    SEMINARIS DOCENTS DE CASO 03/04 - 2Q NÚM GRUP: Facultat d´Informàtica de Barcelona - Departament AC - UPC Fitxa corresponent al treball sobre un tema d´actualitat dins del tema 6 del curs. Aquest treball també portarà associada una presentació obligatoria del mateix (d’uns 10’) i forma part de la nota NS tal com es va indicar a principi de curs. Aquest treball es pot fer en grups d’1, 2 o 3 persones. Cada grup serà responsable de supervisar l’adequació de la presentació d’un altre grup. El fet de lliurar aquest treball implica l´acceptació de fer-ne una presentació d’un màxim de 10’ a classe a partir de les transparències powerpoint que podran ser distribuïdes com a documentació docent als alumnes de CASO i formar part dels coneixements evaluables de l´assignatura . ELECCIÓ TREBALL: Cal que envieu un mail (amb el format especificat a l´avís del Racó) amb títol de la presentació, els noms, preferència matí/tardai breu descripció a [email protected] . Tot això abans del dimarts 18 de Maig 2004. Després d´aquesta data ja no s'acceptaran. LLIURAMENT: El termini de lliurament dels treballs és fins diumenge 23 de Maig 2004. Els treballs es lliuraran per correu elect rònic a l´adreça [email protected] preferiblement en format PDF. Tamb é es pot enviar en powerpoint usant la plantilla que podeu trobar a http://docencia.ac.upc.es/FIB/CASO/seminaris/TransSEMcaso.ppt o OpenOffice. Tot treball no lliurat dins del termini establert es considerarà no lliurat. PRESENTACIONS ANTERIORS: http://docencia.ac.upc.es/FIB/CASO/seminaris/SeminarisCASO.htm MEMBRES
    [Show full text]
  • Study of Mosix Software Tool for Cluster Computing in Linux
    ISSN (Online) 2278-1021 ISSN (Print) 2319 5940 International Journal of Advanced Research in Computer and Communication Engineering Vol. 4, Issue 10, October 2015 Study of Mosix Software Tool for Cluster Computing In Linux Vinayak D. Shinde1, Priyanka Tarmale2, Shahista shaikh3 H.O.D., Department of Computer Engineering, Shree L.R. Tiwari College of Engineering, Mumbai, India1 Student of M.E, Department of computer Engineering, Shree L.R. Tiwari College of Engineering, Mumbai, India2, 3 Abstract: Mosix conveniently supports a multi-user time-sharing environment for the execution of both sequential and parallel task. it is designed to respond to variations in the resource usage among the nodes by migrating processes from one node to another. Mosix use for load-balancing and to prevent memory depletion from any node .The core of the Mosix technology is the potential of multiple servers (nodes) to work cooperatively. Mosix is a system for sustaining cluster computing. It consists of kernel-level, adaptive resource sharing algorithms that are setup for superiority, overhead-free scalability and ease-of-use of a scalable computing cluster of a single system. It is consider as a leader in the field of high performance computing community. Keywords: Cluster computing, Mosix Technology, scalability in Mosix. 1. INTRODUCTION The mosix technology provide more than two nodes goal is to improve overall (cluster -wide) performance and work combine as they were part of single system. In order to create a convenient lot of different users, townhouse to understand what Mosix does, let us compare a Shared environment for the execution of both sequential and Memory (SMP) multicomputer and a CC.
    [Show full text]