#========================================================================
#
# r00 Config file for cpu-rate.
#
#========================================================================
#                         INSTRUCTIONS  
#========================================================================
# All variables are set according to single values as
# VARIABLENAME = VALUE
# (where value may be a text string with spaces in "'s on a single line)
# or lists of values as
# VARIABLENAME = (
#   VALUE1
#   VALUE2
#    ...
# )
# where again VALUE* can be a text string with spaces in "'s on a
# single line (where appropriate, of course).  In some cases there
# MUST be a correspondance in order and number between list elements;
# for example there MUST be a DISK and DISKTYPE entry for every disk
# registered, and there MUST be a NETWORK, NICTYPE and NETHUB entry for
# every network device.
#
# Comments can be any line that BEGINS with a "#" (like this one).
#
# If this format isn't followed, other scripts and parsers will break,
# so be careful!
#
#========================================================================
# The following variables describe the system itself and are likely
# set correctly (from uname).
#========================================================================
HOSTNAME = r00
CPUFAMILY = i686
SYSTEM = Linux
KERNEL = 2.4.18-10smp
#========================================================================
# The motherboard will have to be entered by hand, if you know it at all.
# Since different motherboards have different clocks and chipsets,
# it certainly matters to a number of measures of system performance.
#========================================================================
MOTHERBOARD = Unknown
#========================================================================
# This following was pulled from /proc/cpuinfo.  The values for L1
# cache size are at BEST guesses based on conditionals within the script.
# Please fix them if they are wrong, and if you are competent in perl
# PLEASE consider adding a conditional that correctly sets them for your
# system and send the diffs or fragment to rgb@phy.duke.edu.
#
# Note that you can enable SMP tests by marking any or all CPU's YES
# in the CPUTEST vector.  This may have no effect, though, so we mark
# them all NO by default.  This will change when a decent set of SMP
# tests exists...:-)
#========================================================================
NUMCPUS = 2
CPUTYPE = (
  "AMD Athlon(tm) MP 1900+"
  "AMD Athlon(tm) Processor"
)
CPUVENDOR = (
  AuthenticAMD
  AuthenticAMD
)
CPUMHZ = (
  1600.063 MHz
  1600.063 MHz
)
CPUL1DATA = (
  Unknown
  Unknown
)
CPUL1CODE = (
  Unknown
  Unknown
)
CPUL2SIZE = (
  256 KB
  256 KB
)
CPUTEST = (
  NO
  NO
)
#========================================================================
# The total memory comes from /proc/meminfo, but the MEMCLOCK and 
# MEMTYPE guesses and are quite possibly wrong.  Once again, at least
# check them carefully and set them appropriately and if you know perl
# consider adding conditionals to the config-host script to set them
# automagically (sending diffs or fragments to rgb@phy.duke.edu).
#
# MEMTEST specifies the amount of memory to test with memory benchmarks,
# if any are available (this is really expected to be useful to the
# lmbench suite, where I'm hoping to contribute this whole suite of
# scripts and tests).  MEMTESTTYPE can be SLOW (the default, which does
# a good job and doesn't take to long for small blocks of memory) or 
# FAST which is sloppier but might not take forever if you are testing
# a lot of memory.  MEMTEST should be comfortably larger than your L2
# cache size and comfortably smaller than your total AVAILABLE memory
# (the entry marked as column=free, row=-/+ buffers/cache by the "free"
# command on a linux box).
#========================================================================
MEMTOTAL = 1031 MB
MEMCLOCK = Unknown MHz
MEMTYPE = Unknown
MEMTEST = 16 MB
MEMTESTTYPE = SLOW
#========================================================================
# The config script parses /var/log/dmesg to extract disk information for
# ide disks.  This works pretty well for the ide disks I have to test on
# a system that saves the boot message in /var/log/dmesg.  An utter lack
# of standards for driver startup messages from scsi controllers makes this
# very difficult to arrange automagically for SCSI devices.  I'd love to
# have contributions from anybody who has a clever idea of how to arrange
# this, but most of the solutions I can contrive require something 
# to be run (e.g. fdisk -l /dev/sd?) that requires root privileges.  Once
# again, it would really be very nice if a "standard form" list of devices
# was maintained by the kernel that indicated (where possible) the device
# name, manufacturer, part number, size, speed, driver, and so forth.  This
# needn't be a formal "registry" in that the system uses it at all, but it
# would tremendously increase the information available to users, admins,
# engineers and programmers outside of rootspace.  Oh, well.
# 
# As before, one can enable disk-based benchmarks to be run on any
# disks in the DISK list via the associated DISKTEST list.  We currently
# assume that all disks should be tested, if possible.
#========================================================================
DISK = (
  /dev/hda
)
DISKTYPE = (
  "78165360 sectors (40021 MB) w/2048KiB Cache, CHS=77545/16/63, UDMA(100)"
)
DISKTEST = (
  YES
)
#========================================================================
# Networks just plain cannot be automagically identified in any sane way.
# The one place that they are almost always identified is in 
# /var/log/messages, but logfiles are typically rotated and may even be
# stored on a completely different system so the required information may
# have long since gone away.  Network drivers inserted as modules do not
# typically log their startup messages into /var/log/dmesg.  Even those
# startup messages don't typically tell a user useful little tidbits like
# whether the connection is (e.g.) 10 or 100 Base full or half duplex, and
# finally even if one DOES have the network drivers' startup messages
# handy, they aren't in anything like a standard form that can be uniformly
# parsed.  Sigh.
#
# I can see no alternative, then, to entering all of this by hand, and I
# cannot even tell you how to go about determining the values you should
# enter short of suggesting that you look in /var/log/dmesg or
# /var/log/messages (quite possibly after restarting your network from
# the point of module insertion up or even rebooting).  The entries below
# are therefore ALL DUMMIES (note the comment "#" signs) and must be
# edited to be functional.
#
# Note also that one MUST select the NETWORK(s) itself from the following
# list:
#  ethernet                aka 10baseT, thinnet, thicknet, etc
#  ethernet-100            aka 100baseT, 100VG
#  ethernet-1000           gigabit ethernet
#  myrinet
#  fddi                    aka cddi
#  atm
#  hippi
#  other                   (describe in NICTYPE and/or NETHUB)
# to facilitate parsing by things that might need to know later.  Feel
# free to send me suggestions for new entries (preferrably with descriptions)
# at rgb@phy.duke.edu.
#
# To enable a test of a network device, enter the name of a target host
# in the NETTEST vector in the appropriate slot.  rsh or ssh (and rcp or
# scp) must work between the current host and the target host for the
# user conducting the benchmark, usually/ideally root (to enable the
# disk tests in lmbench).
#========================================================================
NETWORK = (
  # ethernet-100
  # other (sneakernet)
)
NICTYPE = (
  "# Lite-On 82c168 PNIC rev 32"
  "# Nike ACG Sport Sandals, size 11"
)
NETHUB = (
  "# Netgear FS108 Fast Ethernet Switch"
  "# The main hall upstairs"
)
NETTEST = (
  # eve
  # NO
)
#========================================================================
# NOTES is a catchall where you can enter whatever you like to describe
# your system that isn't covered above.  This can be something as simple
# as "This system belongs to Robert G. Brown <rgb@phy.duke.edu>", or as
# complicated as a detailed description of a beowulf for which this system
# is a node.  It can be nothing at all.  As you can see, quotes are not
# necessary although one may have to use care with symbols like @ or
# $ as they are used by perl.  
# 
# Be careful (as always) to preserve the general format of single lines
# sandwiched between the ()'s or later scripts will be unable to parse 
# it correctly.
#========================================================================
NOTES = (
   This system has been initialized, but many variables (in particular,
   the network variables) are not set or are set incorrectly.  Edit the
   configuration file in config/Unknown to complete the installation.
   You should probably remove or edit this set of notes as well to show
   that you've done so.
)
#========================================================================
