On Aug 3, 2007, at 2:49 AM, Darren J Moffat wrote:
> eric kustarz wrote:
>> Sure thing. If we allow benchmarks to have their own directory
>> (such as /usr/benchmarks/libmicro/), then we can allow that
>> benchmark to do what it wants in that directory. This would make
>> porting much easier, less mangling of the source.
>> It turns out that in filebench there is just a simple #define that
>> specifies where everything under /usr/lib/filebench lives. So
>> moving from platform to platform will be easy (if /usr/lib/
>> filebench is not an option).
>
> Specifically for filebench is there are reason to spread it around
> with parts in /usr/benchmarks/ and parts in /usr/lib ? I don't yet
> see any value in that.
>
Having to use /usr/lib was historical (back when we had /usr/bin/
filebench).
If others would like, i can certainly put everything in /usr/
benchmarks/filebench. That might be a nice precedent to set for the /
usr/benchmarks directory.
We would then have the following executables:
/usr/benchmarks/filebench/bin/filebench (executable perl script)
/usr/benchmarks/filebench/bin/go_filebench (isaexec link)
/usr/benchmarks/filebench/bin/{i386,amd64,sparcv9}/go_filebench
(executable binary)
And the following subdirectories:
/usr/benchmarks/filebench/config
/usr/benchmarks/filebench/scripts
/usr/benchmarks/filebench/workloads
eric
