[EMAIL PROTECTED] wrote:
> Hi Drew,
> I took a look at your webrev and in general I think this looks good.
>
> - In the two .f files you added, would it make sense to instruct the
> user that $iosize is being randomly set, and they shouldn't adjust the
> value? What happens in those two cases if the user sets $iosize?
>
If you type something like,: set $iosize=mumble,
it will give you a warning and not do anything. However, you can type:
set $iosize.gamma=<new gamma value>, for instance, to set a new gamma
value. Perhaps I should add the options that make sense to the "usage"
field. I thought about printing more of the default parameters out but
that would get rather messy. Hmmm, I guess I could allow individual
parameters to be accessed with $<name>.<parameter>, so a couple lines like:
usage " set \$iosize.min=<minum> defaults to $iosize.min"
usage " set \$iosize.gamma=<gamma> defaults to $iosize.gamma"
which would print out as:
set $iosize.min=<minum> defaults to 1024
set $iosize.gamma=<gamma> defaults to 1500
That way the workload's author could only include parameters that make
sense for the particular workload.
Comments?
Drew
> Nice work,
>
Thanks!
> -j
>
> On Tue, Jan 29, 2008 at 11:09:52AM -0800, Andrew Wilson wrote:
>
>> I have developed a new "random variables" feature for FileBench. A
>> general discussion of the approach is available at:
>>
>> http://www.solarisinternals.com/wiki/images/1/1d/FileBench_Random_Variables.pdf
>>
>> See the section headed "Current Proposal and Prototype" on page 7 of the
>> document for a description of the feature, and references to some of the
>> key design concepts described in other sections.
>>
>> The webrev is located at:
>>
>> http://cr.opensolaris.org/~dreww/filebench_random_variables/
>>
>> Thanks,
>> Drew
>> _______________________________________________
>> perf-discuss mailing list
>> [email protected]
>>
_______________________________________________
perf-discuss mailing list
[email protected]
