Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Solaris Ipc Final

Solaris Ipc Final

Ratings: (0)|Views: 146 |Likes:
Published by Zarnigar Altaf

More info:

Published by: Zarnigar Altaf on Feb 03, 2011
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Solaris Operating System:-
Solaris is a Unix operating system originally developed by Sun Microsystems. Itsuperseded their earlier SunOS in 1992. Oracle Solaris, as it is now known, has beenowned by Oracle Corporation since Oracle's acquisition of Sun in January 2010.Solaris was historically developed as proprietary software, then in June 2005 SunMicrosystems released most of the code base under the CDDL license, and founded theOpen Solaris open source project. With Open Solaris Sun wanted to build a developer and user community around the software. After the acquisition of Sun Microsystems inJanuary 2010, Oracle decided to discontinue the Open Solaris distribution and thedevelopment model. As a result, the Open Solaris community forked the Open Indiana project, as part of the Illumes Foundation. However, starting with Solaris 11, updates tothe Solaris source code will still be distributed under the CDDL license, after full binaryreleases are made. Oracle will also begin a technology partner program, called OracleTechnology Network (OTN), to permit their industry partners access to the in-development Solaris source code.
What is Inter Process Communication?
Official definition:
Inter process communication (IPC) is used for programs to communicate data to eachother and to synchronize their activities. Semaphores, shared memory, and internalmessage queues are common methods of inter process communication.
What it means:
IPC is a method for two or more separate programs or processes to communicate witheach other. Or we can say that Inter-process communication (IPC) is a set of techniquesfor the exchange of data among multiple threads in one or more processes. Processes may be running on one or more computers connected by a network. This avoids using realdisk-based files and the associated I/O overhead to pass information. Like a file, youmust first create or open the resource, use it and close it. Like real files, the resourceshave an owner, a group, and permissions. Until you remove the resource it continues toexist. Unlike real disk-based files, semaphores, message queues and shared memory donot persist across reboots. The method of IPC used may vary based on the bandwidth andlatency of communication between the threads, and the type of data being communicated.
Reasons to use Inter Process Communication:
Use IPC’s when you need to talk between programs, you want the talking to be fast, andyou do not want to write the code to manage the low-level details of communication between the processes. Since these are kernel routines, the kernel will take care of thedetails of the communication. For example, when you are waiting for a resource that is protected by a semaphore to become available, if you request access and the resource iscurrently in use, the kernel will place you in a waiting queue. When the resource becomes available, the kernel unblocks your process and you can continue. The kernelalso ensures that operations are atomic, which means that a test and increment operationto set a semaphore cannot be interrupted.1
There are several main reasons for providing an environment that allows processcooperation:Information sharingSpeedup;Modularity;Convenience; andPrivilege separation.
IPC’s in solaris (os):-
Interprocess communication (IPC) encompasses facilities provided by the operatingsystem to enable the sharing of data (shared memory segments), the exchange of information and data (message queues), and synchronization of access to sharedresources (semaphores) between processes and threads on the same system. Contrast IPCto networking-based facilities, such as sockets and RPC interfaces, which enablecommunication over a network link between distributed systems. Early IPC facilitiesoriginated in AT&T Unix System V, which added support for shared memory,semaphores, and message queues around 1983. This original set of three IPC facilities isgenerally known as System V IPC. Over time, a similar set of IPC features evolved fromthe POSIX standards, and we now have POSIX semaphores, shared memory, andmessage queues. The System V and POSIX IPCs use different APIs and are implementeddifferently in the kernel, although for applications they provide similar functionality.Other facilities for interprocess communication include memory mapped files, named pipes (also known as FIFOs), Unix domain sockets, and recently added Solaris Doors,which provides an RPC-like facility for threads running on the same system. Eachmethod by which an application can do interprocess communication offers specificfeatures and functionality which may or may not be useful for a given application. It’sup to the application developer to determine what the requirements are and whichfacility best meets those requirements. Doors are a low-latency method of invoking a procedure in local process. A door server contains a thread that sleeps, waiting for aninvocation from the door client. A client makes a call to the server through the door,along with a small (16 Kbyte) payload. When the call is made from a door client to adoor server, scheduling control is passed directly to the thread in the door server. Oncea door server has finished handling the request, it passes control and response back tothe calling thread. The scheduling control allows ultra-low-latency turnaround becausethe client does not need to wait for the server thread to be scheduled to complete therequest.2
1982Sun UNIX 0.7First version of Sun’s UNIX, based on 4.BSDfrom UniSoft.Bundled with the Sun-1, Sun’s first workstation based on the Motorola 68000 processor;SunWin-dows GUI.1983SunOS 1.0Sun-2 workstation, 68010 based.1985SunOS 2.0Virtual file system (VFS) and vnode framework allows multiple concurrent file system types.NFS implemented with the VFS/vnode frame-work.1988SunOS 4.0New virtual memory system integrates the filesystem cache with the memory system.Dynamic linking added.The firstSPARC-based Sun workstation, theSun-4. Support for the Intel-based Sun 386i.1990SunOS 4.1Supports the SPARCstation 1+, IPC, SLC.OpenWindows graphics environment1992SunOS 4.1.3Asymmetric multiprocessing (ASMP) fosun4msystems (SPARCstation-10 and -600 series MP(multiprocessor) servers).1992Solaris 2.0Solaris 2.x is born, based on a port of System VRelease 4.0.VFS/vnode, VM system, intimate shared mem-ory brought forward from SunOS.Uniprocessor only.First release of Solaris 2, version 2.0, is a desk-top-only developers release.1992Solaris 2.1Four-way symmetric multiprocessing (SMP).1993Solaris 2.2Large (> 2 Gbyte) file system support.SPARCserver1000andSPARCcenter2000(sun4d architecture).1993Solaris 2.1-x86Solaris ported to the Intel i386 architecture.3

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->