Shared memory based Synchronization
Java
- mutual exclusion available.
- mixture of high-level object oriented feature and low concurrency primitives.
- General notification feature.
Ada
- has high-level synchronization support (projected object) which scales to large size of project.
- Full compiler support(potential dead lock analysis)
- Low-level semaphore for very special use.
High performance Computing(HPC)
- keep cpu as busy as possible.
- Avoid contention on spare resources.
- Data is assigned to individual process rather than process synchronizing on data.
- the Data integrity is achieved by keeping the CPU nodes in approximate "lock- step", but we still need to re-sync concurrent entities.
Synchronization Model(Message-based synchronization)
Synchronous
- Sender waiting
- Receiver waiting
Until another side is available and another side acknowledge to finish it.
Simulated by asynchronous:
- both process suspend themselves until the transaction is completed.
- as there is no immediate communication takes place, the process will never actually synchronized.
- the sender process know when it is finished.
Asynchronous
- Message is not transferred directly.
- A buffer is required to store the messages.
- care about the buffer overflow and buffer size.
Simulated by synchronous message
- intermedia is able to accept message at all times.
- intermedia also need to send message out on request.
Remote invocation
- delay the sender or receiver until the first rendezvous point.
- pass parameters.
- keep the sender blocked until the receiver finished its own process.
- pass result
- release both process
Simulate by asynchronous messages:only need to simulate 2 synchronous messages.
Remote invocation(No results)
Shorter form of Remote invocation which does not wait for results to be passed back.
Both Remote invocations are actually synchronized at the time of invocation.
Simulate by asynchronous messages:only need to simulate 1 synchronous messages.
Summary
If we want to simulate the Synchronization: use synchronous message and remote invocation.
or our purpose is to last message only then we use the Asynchronous message.
Communication model
one to one: buffer, queue, synchronization
one to many: multicast
one to all: broadcast
many to one: local server, synchronization
all to one: general server, synchronization
many to many: general-network or bus-system
Ada supports remote invocations in form of : entry point in the tasks and full set of parameter profiles supported.
rendezvous:2 tasks synchronized at the beginning of the remote invocation.
extended rendezvous:the calling task block is blocked until the remote routine is finished.
About the task entry
- task entry can call other blocking operations.（protected entry can't）
- "count" is defined but only inside of the task which has the entry.
- entry family and private entry is supported.
the difference between entry in the protected object and task is the fairness.
