Browse Prior Art Database

Shared Text Across Multiple Systems

IP.com Disclosure Number: IPCOM000127405D
Original Publication Date: 2005-Aug-29
Included in the Prior Art Database: 2005-Aug-29
Document File: 2 page(s) / 26K

Publishing Venue

IBM

Abstract

Shared Text Across Multiple Systems

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

Shared Text Across Multiple Systems

Currently, multiple operating systems that may be running on different partitions, or possibly even different hardware, run on their own and use existing means, such as TCP/IP, to communicate with each other. Each separate system must load its own copies of libraries and commands according to what the installation of its operating system requires, and each of these software entities requires the appropriate amount of RAM, cache, and other limited hardware resources in which to load itself. This introduces a problem of the efficiency of hardware use, which is not as apparent on systems running on separate hardware, but is blaringly obvious in the situation in which multiple operating system instances run on the same hardware. On these systems, one could ask the question, "If I have a limited amount of RAM, why must so many of the common components of similar operating systems be duplicated in each running system?" These duplicate components in similar operating systems use up a large amount of RAM and other hardware resources that could be devoted to more useful applications, thus resulting in overhead from simply running different operating systems.

A solution to this problem is to introduce a shared global area of RAM that can be addressed by each individual system as if it were on its own bus. In this shared area of RAM, a "supervisor" operating system instance could load any number of libraries that other compatible systems could address and reference. The actual libraries that are shared and the privilege that other system instances are granted to use certain shared libraries are manually allocated by a superuser on the supervisor system. Thus, the compatibility of a certain library with a client system instance is determined by this superuser. Take for instance a common library such as libc- the superuser of the supervisor partition would load a libc with which a certain number of other physically accessible systems (through some means such as PHYP) are deemed compatible, and allocate these libraries to them for their shared use. These other systems, instead of loading...