Shared Memory
Shared Memory
Shared Memory
It gives the impression of a single memory. Programmers access the data across the
network using only read and write primitives.
Programmers do not have to deal with send and receive communication primitives
and the ensuing complexity of dealing explicitly with synchronization and
consistency in the message passing model.
A part of each computer’s memory is earmarked for shared space, and the
remainder is private memory.
If a block of data needs to be moved, the system can exploit locality of reference to
reduce the communication overhead.
DSM provides portability of programs written using DSM. This portability arises
due to a common DSM programming interface, which is independent of the
operating system and other low-level system characteristics
When multiple processors wish to access the same data object, a decision about how
to handle concurrent accesses needs to be made. If concurrent access is permitted by
different processors to different replicas, the problem of replica consistency needs to
be addressed.
1. Programmers are aware of the availability of replica consistency models and from
coding their distributed applications according to the semantics of these models.
3. Since the control is given to memory management, the programmers lose the ability
to use their own message-passing solutions for accessing shared objects.
Selecting the locations for replication to optimize efficiency from the system’s
viewpoint.
Determining the location of remote data that the application needs to access, if full
replication is not used.
Reducing communication delays and the number of messages that are involved under the
covers while implementing the semantics of concurrent access to shareddata.