Dinero cache simulator-Computer Architecture

【问题描述：】

PART A.

The Dinero cache simulator is available on the COE Solaris system (machines alpha, beta). The

following information is for using dineroIII (which is the default dinero installed on COE Solaris

systems). You will also find dineroIV installed on both Solaris and Linux machines. Please use

dineroIII for this assignment. You are welcome to experiment with dineroIV.

Dinero allows you to configure a cache using command line arguments (see attached info on

Dinero). The simulator takes as input an address trace. The Dinero input format "din" is an

ASCII file with one LABEL and one ADDRESS per line. The rest of the line is ignored so that it

can be used for comments.

LABEL = 0 read data

= 1 write data

= 2 instruction fetch

= 3 escape record (treated as unknown access type)

= 4 escape record (causes cache flush)

0 <= ADDRESS <= ffffffff where the hexadecimal addresses are NOT preceded by "0x."

Here are some examples:

2 0 This is an instruction fetch at hex address 0.

0 1000 This is a data read at hex address 1000.

1 70f60888 This is a data write at hex address 70f60888.

Make sure to use lowercase.

After creating a trace file (e.g., trace.txt), you run Dinero as follows:

dinero –i16KB –d32KB –b32 < trace.txt

This will simulate a 16KB instruction cache and a 32KB data cache, each with a 32 byte block

size.

Your job is to generate reference streams in Dinero's din format (see description provided with

trace) and produce the following (where you are asked to generate an address stream, submit in

your report enough of the trace so that we can understand the pattern you are using – do not

submit the full trace since it will only waste paper):

1. Assume that you have a direct-mapped 16KB instruction cache (32B block). Generate an

address stream that will touch every cache line once, but no more than once.

2. Assume the same instruction cache organization as in (1), but now the instruction cache is 2-

way set associative, with LRU replacement. The total cache space is still 16KB with a 32B

block, but now you have 1/2 the number of indices. Generate an address stream that touches

every cache index only 8 times, producing 5 misses and 3 hits, but only accesses 3 unique

addresses per index.