===================
ABOUT THIS DOCUMENT
===================

This file is a supplemental document that describes how to use the
Solaris* version of the Dynamo workload generator.  For general
information about Dynamo and Iometer, see the Iometer User's Guide
(Docs/Iometer.htm or Docs/Iometer.pdf) and related files (README.txt,
RevHist.txt, License.txt, etc.).  

The latest version of Iometer, including the documentation, can be
obtained from the Intel Developers' Web Site at the following URL:

    http://developer.intel.com/design/servers/devtools/iometer/ 

Send questions, comments, and bug reports to "iometer@intel.com".

The Solaris version of Dynamo is covered by the Intel Software License
Agreement (License.txt) which you must agree to in order to download
or run Iometer.  Please read this file, and do not use the software unless
you agree to its terms.

The information in this file is provided by Intel as a convenience to
Intel's general customer base.  Intel assumes no responsibility for any
errors which may appear in the document nor does it make a commitment to
update the information contained herein.

* Third-party brands and names are the property of their respective owners.

====================================
ABOUT THE SOLARIS* VERSION OF DYNAMO
====================================

Dynamo is an I/O workload generator that runs under the control of a
separate control program, called Iometer.  Iometer provides the user
interface, tells Dynamo what to do when the test starts, and gathers the
data at the end of the test.  Dynamo cannot be used without Iometer.  

Iometer runs only under Microsoft* Windows NT 4.0 or above.  This means
that you *must* have a Windows NT machine to use the Solaris version of
Dynamo.  The NT machine and Solaris machine(s) must be able to access
each other over the network (TCP/IP protocol).  Iometer and Dynamo must
have the same version number to work together.

The CPU statistics "% Interrupt Time" and "% DPC Time" are not currently
collected by the Solaris version of Dynamo.

The "dynamo" file in this directory is a binary Solaris executable.  It
runs on Solaris version 2.6 or above.  Only the Intel Architecture
version of Solaris is supported at this time; no SPARC executable is
available.

=================
INSTALLING DYNAMO
=================

To install Dynamo on a Solaris machine, simply copy the single executable
file "dynamo" to any directory on that machine.

===============
INVOKING DYNAMO
===============

You can run Dynamo as root or as a normal user.  

 * If you run Dynamo as a normal user, you will only be able to test
   logical disks (mounted file systems) whose root directory is writable
   by that user, not physical disks.  You can also test TCP/IP
   networking, but the "TCP Segments Retrans. per Sec." statistic is
   not collected (its value is always zero).

 * If you run Dynamo as root, you can test all mounted file systems, all
   non-empty physical disks, and TCP/IP networking, and all statistics
   are collected.

To use Dynamo, you must also invoke Iometer on the Windows NT machine
(by double-clicking on the Iometer.exe icon).  Iometer automatically
launches a copy of Dynamo on the local machine; if you do not want this
Dynamo, you can remove it by clicking on it in Iometer's Topology panel
and pressing the "Disconnect Selected Manager or Worker" button.

Once Iometer is up and running, you invoke the Solaris version of Dynamo
and tell it where to find its controlling Iometer as follows:

	# dynamo <iometer-machine-name>

You can use a fully-qualified name (for example, "fred.mycorp.com") or a
partially-qualified name (just "fred"), depending on what is necessary
in your local network configuration.

After Dynamo has started up and reported its disks and network
interfaces to Iometer, it appears in the Iometer GUI as a "manager".
See the "Iometer User's Guide" for information on what to do next.

=============
LOGICAL DISKS
=============

Mounted file systems appear in the Iometer GUI as logical disks (yellow
disk icons).  The disk name in the GUI consists of the mount point
pathname followed by the file system type in square brackets, for example:

	/usr [ufs]

If the file system type is "[ufs, BUF]", that means that the
"forcedirectio" option was not specified when the file system was
mounted.  If this option is not specified, access to the file system is
always buffered, and any results obtained using this file system will
not be comparable to the unbuffered I/O used under Windows NT.  See the
mount_ufs(1M) manpage for more iformation on the "forcedirectio" option.

As with Windows NT, logical disks are accessed through a file called
"iobw.tst" at the root of the file system.  If this file does not exist,
the yellow disk icon is shown with a red slash through it.  If you select
this disk for a test, the test will begin by creating the "iobw.tst" file
and expanding it until the drive is full.  See the "Iometer User's Guide"
for more information.

==============
PHYSICAL DISKS
==============

Raw disk devices appear in the Iometer GUI as physical disks (blue disk
icons).  Only the devices /dev/rdsk/*p0 are available for testing, and a
device appears only if it is accessible (that is, there is a
corresponding physical device and it is not disabled) and is completely
empty (that is, it contains no partitions).  

The disk name in the GUI is the basename of the device, for example:

	c0t4d0p0

For bus-type controllers (SCSI, Fibre Channel, etc.) the parts of this
name have the following meanings:

	c - Controller number
	t - Physical bus target number
	d - Drive number or Logical Unit Number (LUN)
	p - Partition number

For IDE drives (non-bus controllers), the names are of the form c0d0p0
(no target number).

As with Windows NT, physical disks are accessed directly, without
creating an "iobw.tst" file, and access to physical disks is always
unbuffered.  Testing with physical disks is recommended.

=================
TCP/IP NETWORKING
=================

TCP/IP network testing under Solaris works exactly as documented in the
"Iometer User's Guide", except that the "TCP Segments Retrans. per
Sec." statistic is not collected unless Dynamo is run by root.

Note that Iometer does not check that Dynamos can access each other
using the specified addresses (for example, they may be on different
subnets).

=========================================
VIRTUAL INTERFACE ARCHITECTURE NETWORKING
=========================================

Virtual Interface Architecture network testing under Solaris is
currently unsupported, because the Virtual Interface Architecture is
currently unimplemented under Solaris.

- END OF FILE -
