Parallel Virtual Machine PVM
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Electrical Fan
Active In SP

Posts: 438
Joined: Aug 2009
10-10-2009, 04:42 PM

Parallel Virtual Machine (PVM) is software system that allows a homogenous (same type) or heterogeneous (different types) networks of computers to be used as a single computational resource . The individual computers may be interconnected by a variety of networks such as Ethernet or FDDI. PVM is used to build and manage the virtual parallel machine and provide the necessary message passing communication. By sending and receiving messages, multiple tasks can be used co-operatively to solve problems in parallel. Under PVM a network of workstations can be used as a single distributed memory computer. The individual machines may have shared or local. This can be used to solve problems which need high computational power
Use Search at wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion
geethu sasidharan
Active In SP

Posts: 1
Joined: Jun 2010
30-07-2010, 09:49 PM

sir, can you please send me report of parallel virtual machine.
ujjwal kumar
Active In SP

Posts: 1
Joined: Mar 2011
08-03-2011, 12:10 PM

send me a report on parallel virtual machine
rashu iyengar
Active In SP

Posts: 8
Joined: Feb 2011
13-03-2011, 09:07 PM

please send me the detailed report on seminar and presentation topic Parallel Virtual Machine PVM.
seminar class
Active In SP

Posts: 5,361
Joined: Feb 2011
23-04-2011, 09:44 AM

.docx   REPORT-SRAVAN.docx (Size: 68.92 KB / Downloads: 51)
PVM (Parallel Virtual Machine) is a software environment for heterogeneous distributed computing. It allows a user to create and access a parallel computing system made from a collection of distributed processors, and treat the resulting system as a single virtual machine (hence the name, parallel virtual machine).
The hardware in a user's virtual machine may be single processor workstations, vector machines or parallel supercomputers or any combination of those. The individual elements may all be of a single type (homogeneous) or all different (heterogeneous) or any mixture, as long as all machines used are connected through one or more networks. These networks may be as small as a LAN connecting machines in the same room, as large as the Internet connecting machines across the world or any combination. This ability to bring together diverse resources under a central control allows the PVM user to divide a problem into subtasks and assign each one to be executed on the processor architecture that is best suited for that subtask.
PVM is based on themessage-passing model of parallel programming. Messages are passed between tasks over the connecting networks.
User's tasks are able to initiate and terminate other tasks, send and receive data, and synchronize with one another using a library of message passing routines. Tasks are dynamic (i.e. can be started or killed during the execution of a program), even the configuration of the virtual machine (i.e. the actual machine that are part of your PVM) can be dynamically configured.
"The first version of PVM was written during Summer of 1989 at Oak Ridge National Laboratory. It was not released, but was used in applications at the lab."
"Version 2 was written from scratch during February 1991 at the University of Tennessee, Knoxville, and released in March of that year. It was intended to clean up and stabilize the system so that external users could benefit."
"After a year and a half of continuing research we felt that we had reached a limit in being able to add to PVM version 2. Version 3 was redesigned from scratch, and a complete rewrite started in September 1992, with first release of the software in March 1993. While similar in spirit to version 2, version 3 includes features that didn't fit the old framework - most importantly fault tolerance, better portability and scalability."
Principles upon which PVM is built are the following-
• User-configured host pool : The application's computational tasks execute on a set of machines that are selected by the user for a given run of the PVM program. Both single-CPU machines and hardware multiprocessors (including shared-memory and distributed-memory computers) may be part of the host pool. The host pool may be altered by adding and deleting machines during operation (an important feature for fault tolerance).
• Translucent access to hardware: Application programs either may view the hardware environment as an attributeless collection of virtual processing elements or may choose to exploit the capabilities of specific machines in the host pool by positioning certain computational tasks on the most appropriate computers.
• Process-based computation: The unit of parallelism in PVM is a task (often but not always a Unix process), an independent sequential thread of control that alternates between communication and computation. No process-to-processor mapping is implied or enforced by PVM; in particular, multiple tasks may execute on a single processor.
• Explicit message-passing model: Collections of computational tasks, each performing a part of an application's workload using data-, functional-, or hybrid decomposition, cooperate by explicitly sending and receiving messages to one another. Message size is limited only by the amount of available memory.
• Heterogeneity support: The PVM system supports heterogeneity in terms of machines, networks, and applications. With regard to message passing, PVM permits messages containing more than one datatype to be exchanged between machines having different data representations.
• Multiprocessor support: PVM uses the native message-passing facilities on multiprocessors to take advantage of the underlying hardware. Vendors often supply their own optimized PVM for their systems, which can still communicate with the public PVM version.
Each machine that will participate in the PVM system must be executing a pvmd. It is sufficient for a user to execute this daemon in their user space.
The PVM system is started on a single machine (using the pvm console command). That single machine is used to start all other pvmd's in the system, via a host file. PVM uses rsh or ssh to start these daemons.
Machines may share a file system. The binary executables for different architectures, including the PVM commands, are stored in architecture specific directories.
The pvmd looks in the appropriate architecture directory when it needs to execute (spawn) user processes as PVM tasks.

Important Note..!

If you are not satisfied with above reply ,..Please


So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  automated teller machine ppt jaseelati 0 141 10-02-2015, 02:08 PM
Last Post: jaseelati
  virtual keyboared jaseelati 0 162 22-01-2015, 01:51 PM
Last Post: jaseelati
  VIRTUAL P.C seminar projects crazy 4 3,931 08-10-2014, 03:33 PM
Last Post: DorothyKl
Brick Virtual keyboard (Download Full Report And Abstract) computer science crazy 37 31,030 08-04-2014, 07:07 AM
Last Post: Guest
Last Post: seminar project topic
  Memory Management: Overlays and Virtual Memory ppt seminar projects maker 0 490 20-09-2013, 04:57 PM
Last Post: seminar projects maker
  Virtual Memory ppt project girl 1 794 11-09-2013, 03:13 PM
Last Post: seminar projects maker
  Report on Exploiting Dynamic Resource Allocation for Efficient Parallel Data study tips 0 379 21-08-2013, 04:36 PM
Last Post: study tips
  Mobile Virtual Reality Service pdf study tips 0 352 19-08-2013, 04:06 PM
Last Post: study tips
  GPU Computing: The Democratization of Parallel Computing study tips 0 225 02-08-2013, 12:15 PM
Last Post: study tips