Unit 4 Flashcards Preview

My M362 Unit SAQs > Unit 4 > Flashcards

Flashcards in Unit 4 Deck (17):
1

Summarise the advantages and disadvantages of using virtual machines.

The main disadvantage of using virtual machines is the slower execution speed of the program, compared with compiling it directly to machine code that is interpreted by the CPU. Moreover, virtual machines are also subject to backward compatibility problems and to the limitations of the various platforms.

The advantages are that the generated virtual machine code is smaller than the corresponding machine code and can be executed on various platforms without requiring any changes, making it easier for organisations to develop applications for a wide user base. Moreover, virtual machines facilitate the development of applications written in multiple languages and promote the creation of new languages.

2

Why is the new semantics of volatile variables an extension of the old one?

Because a memory barrier on each volatile variable access still forces the variable to be
read from or written to shared memory, as required by the old memory model.

3

Summarise the main points of

(a)
one of the central concerns for correctness of multithreaded applications;

For a multithreaded application to behave correctly, changes made to shared variables by one thread must be visible to all other threads reading those variables.

4

Summarise the main points of

(b)
two problems that affect the achievement of correctness (in threads);

Updates in one thread might not be visible to other threads due to code reordering or because the values’ copies held in local and shared memories are inconsistent.

5

Summarise the main points of

(c)
the generic techniques that address the two problems specified in part (b) below;

Updates in one thread might not be visible to other threads due to code reordering or because the values’ copies held in local and shared memories are inconsistent.

Mutual exclusion serialises accesses and this prevents the side effects of code reordering. To address the inconsistency problem, a memory model defines how value updates are propagated via memory barriers.

6

Summarise the main points of

(d)
the concrete Java mechanisms that implement those techniques below;

 

Mutial exclusion and Memory barriers

Mutual exclusion is imposed by synchronised code. Memory barriers that make the values held locally by the thread consistent with those held in shared memory are created by accessing volatile variables or by synchronising code.

7

Summarise the main points of

(e)
how the mechanisms below in part (d) can be used.

Synchronisation and Memory barriers

Correct behaviour can be guaranteed only if threads synchronise on the same monitor or access the same volatile variable. Code is not reordered across memory barriers, which makes it possible to use volatile variables to flag changes to shared variables.

8

Through which method calls can a Java thread release control?

By calling sleep, yield, wait or join (Unit 2, Section 7).

9

Summarise the main points of

(a)
the two ways of implementing Java threads;

Among the decisions left open by the JVM specification is how to implement Java threads:

they may be green threads, i.e. managed by the JVM,

or native threads, i.e. managed by the operating system.

10

Summarise the main points of

(b)
the corresponding advantages and disadvantages of;

green threads and native threads

Using green threads may be the best option if the underlying platform does not have threads, but the disadvantage is that the JVM implementation becomes more complex.

Using native threads has the advantage of exploiting better the underlying platform resources, in particular if it has multiple processors. On the other hand, native threads make the behaviour of the Java program dependent on the way the operating system schedules and prioritises threads.

11

Summarise the main points of

(c)
the consequences for writing platform-independent programs.

This means that for a program to be truly platform independent it should:

  •  not use thread priorities;
  •  release control – via wait and sleep rather than yield – whenever adequate, to avoid problems if executed on a cooperative multitasking platform;
  •  access shared data only under mutual exclusion, so as to avoid problems if executed on a pre-emptive multitasking platform.

12

Can you recall, from earlier in the course, a context where priority queues might be useful?

Priority queues are useful when implementing process schedulers (Unit 2, Section 5). Each element in the queue consists of a pair of numbers – the unique process ID and the process priority. The next process to be scheduled is the one at the front of the priority queue.

13

What is a re-entrant lock?

A re-entrant lock can be reacquired by a thread that already holds it (Unit 3, Section 4).

14

List some shortcomings of Java’s built-in monitors and how they are addressed by the interfaces and classes of the java.util.concurrent.locks package.

Some disadvantages of the built-in monitors are:

  • no separation of data, lock, and condition variables;
  • one single condition variable per lock;
  • an attempt to acquire a lock cannot be cancelled.

The Lock and Condition interfaces allow the creation of explicit locks that are separate objects, and the creation of multiple conditions per lock. Moreover, the Lock interface allows a thread to timeout on acquiring a lock or to avoid blocking if the lock is not available.

15

Why should the call to wait not be within a simple if?

When a thread T resumes execution after a call to o.wait(), this only means two things: T was notified by some other thread, and T has reacquired the lock on object o. In particular, resumption of execution does not mean that the condition has become true. For example, T might have been woken together with other threads by a notifyAll, and one of those threads may have acquired the lock on o first and invalidated the condition again.

16

What is the simplest way of accessing ‘the ArrayList object via synchronised methods’, as suggested above?

The simplest way is to wrap it using Collections.synchronizedList
(Subsection 3.2).

17

What are the thread-safety levels of LinkedList and CopyOnWriteArrayList mentioned in Subsection 3.2?

LinkedList is thread-compatible, like ArrayList,

while CopyOnWriteArrayList is conditionally thread-safe. The latter is not thread-safe because different threads may see the data structure in different states due to the weakly consistent iterators.

(Page 29)