1 ##############################################################################
3 # @(#)sfs_cifs_rc $Revision: 1.14 $
5 # Specify SFS parameters for sfs runs in this file.
7 # The following parameters are configurable within the SFS run and
10 # See below for details.
12 # Example shows a CIFS run of 100 to 1000 ops/sec
18 CLIENTS="c09-44.sysnet.ucsd.edu"
19 #MNT_POINTS="\\c09-45.sysnet.ucsd.edu\export"
20 MNT_POINTS="\\c09-45.sysnet.ucsd.edu\export \\c09-45.sysnet.ucsd.edu\export \\c09-45.sysnet.ucsd.edu\export \\c09-45.sysnet.ucsd.edu\export"
35 # The following parameters are strictly defined within the SFS
36 # run and reporting rules and may not be changed.
48 # The following parameters are useful for debugging or general system
49 # tuning. They may not be used during during a reportable SFS run.
58 # The default SFS options are implied if no values are assigned to
59 # the variables. The variables and their meaning are as follows.
61 # The following parameters are configurable within the SFS run and
64 # LOAD - array of numbers specifying the NFS loads
65 # (NFS calls per second) to be generated by all clients
66 # combined. The number of consecutive runs equals the size
67 # of the array and the peak load equals the largest value
68 # in the array. (DEFAULT = 60)
69 # PROCS - number of SFS sub-processes to generate NFS
70 # calls (DEFAULT PROCS = 4).
71 # MNT_POINTS - string containing the shares of CIFS-mounted
72 # filesystems on the client which will be used in the test or
73 # it can be set to the name of a file containing a list of
74 # shares. The file should be located in WORK_DIR. The
75 # file should have the following format:
76 # client1 \\svr\share ... \\svr\share
78 # clientN \\svr\share ... \\svr\share
80 # IPV6_ENABLE - If set ("on") then use IP V6 otherwise use IP V4.
81 # (DEFAULT IPV6_ENABLE = "off").
82 # FS_PROTOCOL - File server protocol used "cifs" or "nfs"
83 # (DEFAULT FS_PROTOCOL = "nfs")
84 # NUM_RUNS - number indicating the number of multi-client runs. NUM_RUNS
85 # should only be used if the size of the LOAD array <= 1;
86 # INCR_LOAD - number indicating the load increment factor in NFS call/sec.
87 # The first run generates LOAD calls/sec,
88 # subsequent runs are made with LOAD + (N * INCR_LOAD)
89 # calls/sec; where initial N = 0. INCR_LOAD should
90 # only be used if the size of the LOAD array <= 1.
91 # CLIENTS - string containing client's host names; include the Prime-
92 # Client's host name if you will be using the Prime-Client to
94 # SFS_DIR - string containing the directory path where the SFS
95 # executables are stored; should be the same for all systems
96 # This location is used first, if the binaries are not found
97 # there then it looks in the "binaries" directory.
98 # (DEFAULT SFS_DIR = "bin")
99 # SUFFIX - Suffix for the log files.
100 # WORK_DIR - string containing directory path where the SFS output
101 # files are stored, this should be the same for all systems.
102 # PRIME_MON_SCRIPT - string containing the name of a script used to
103 # control the start and stop of any external SFS processes
104 # like external performance monitors. The sample script
105 # 'sfs_ext_mon' shows the expected semantics of the program.
106 # This variable must refer to an executable on a Windows
108 # PRIME_MON_ARGS - string containing optional arguments that are passed
109 # to the PRIME_MON_SCRIPT.
111 # USERNAME - The user name for mapping the share.
112 # PASSEORD - The password for mapping the share.
113 # DOMAIN - The domain for mapping the share
114 # SFS_NFS_USER_ID - User ID for NFS server. Used only when running on
116 # SFS_NFS_GROUP_ID - Group ID for NFS server. Used only when running on
119 # The following parameters are strictly defined within the SFS
120 # run and reporting rules and may not be changed.
122 # RUNTIME - number of seconds to generate load
123 # (DEFAULT RUNTIME = 300).
124 # TCP - If set ("on") then use NFS/TCP behaviour rather than UDP.
125 # WARMUP_TIME - number of seconds to warmup
126 # (DEFAULT WARMUP_TIME = 300).
127 # ACCESS_PCNT - percent of total file set available for use by i/o
128 # operations that will be accessed.
129 # (DEFAULT ACCESS_PCNT = 20).
130 # APPEND_PCNT - percent of writes that append rather than overwrite
131 # (DEFAULT APPEND_PCNT = 70).
132 # BLOCK_SIZE - number of KB in a block, up to 4 Meg.
133 # (Value is automatically negoitated with the server)
134 # DIR_COUNT - number of files per directory to use for directory
135 # operations (DEFAULT DIR_COUNT = 30).
136 # FILE_COUNT - number of files to use for read and write
137 # operations. By default, number of files is
138 # calculated from the specified LOAD and ACCESS_PCNT.
139 # SYMLINK_COUNT - number of symbolic links to use for symlink
140 # operations (DEFAULT SYMLINK_COUNT = 20).
142 # The following parameters are useful for debugging or general system
143 # tuning. They may not be used during during a reportable SFS run.
145 # DUMP - If set to a non-zero value, dump raw data points at end of
146 # run. (DEFAULT DUMP = 0 ).
147 # LAT_GRAPH - Debug option to enable latency graph logs. May invalidate
148 # results due to overhead of logging. (default "", to
150 # POPULATE - If set ("on") then only populate the file set but do not
152 # PRIME_SLEEP - number of seconds Prime-Client should sleep after starting
153 # and stopping the SFS external monitoring facility and
154 # before sending synchronization message to clients. This is a
155 # provision to allow sufficient time for starting and stopping
156 # other performance monitoring utilities that could be used
157 # during SFS execution.
158 # PRIME_TIMEOUT - number of seconds Prime-Client should wait for a
159 # response from all the clients. Zero indicates the
160 # default should be used.
161 # INIT_TIMEOUT - number of seconds Prime-Client should wait for a
162 # response from all the clients during the INIT phase.
163 # May be changed if needed and will not invalidate the