The <A HREF="Man.html">man page </A> is clear but cluttered with
numerous options.  Here is an introduction for the beginning user:

<P>

Usage:

<PRE>
dinero options_list < input_file
</PRE>

The input file must be in din format, explained in the man page.
DLX trace output is of this form.

<P>

Here are the major options of interest to the beginner:

<P>

<UL>

<LI>
-b block_size:  Block (line) size.

<P>

<LI>

-u unified_cache_size:  Cache size if a single cache is used.  Defaults
to 0.

<P>

<LI>

-i instruction_cache_size:  Instruction cache size if separate caches
are used.  Defaults to 0.

<P>

<LI>

-d data_cache_size:  Data cache size if separate caches are used.
Defaults to 0.

<P>

<LI>

-a associativity_value:  Specifies the set-associativity.  A
direct-mapped cache has associativity 1.  A two-way set-associative
cache has associativity 2.  A fully  associative  cache  has
associativity (cache_size)/block_size.  Defaults to 1, i.e.
direct-mapped.

<P>

<LI>

-w write_policy:  Specify w for write-through, c (``copy back'')
for write-back.  Defaults to c.

</UL>

<P>

The block and cache sizes are in bytes (no special suffix),
kilobytes (`K' suffix) or megabytes (`M' suffix).  For example, specify
-u1M for a 1-megabyte unified cache.

<P>

Other values will be set to defaults.  Replacement policy, for instance,
defaults to LRU, though other choices are available.

<P>

Various amounts of output can be chosen.  The default output type will
report:  the number of read and write requests handled by the cache
(``Demand Fetches''); the number of these which resulted in misses
(``Demand Misses''); the number of words read from memory to the cache
(``Words From Memory''); and the number of words written to memory from
the cache (``Words Copied-Back,'' a term which does NOT refer to
copy-back, i.e. write-back, write policy).  

<P>