Skip to content
Snippets Groups Projects
Commit c69d592f authored by bjschre2's avatar bjschre2
Browse files

Remove unused parboil files

parent 71fe249e
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
hpvm/test/parboil/DIRECTORIES deleted 100644 → 0
+ 0
− 62
View file @ 71fe249e
common/
Shared files
include/
Shared include files
mk/
Shared makefiles for specific languages
python/
Shared python code
src/
Source code of shared libraries
platform/
Shared makefiles for different execution platforms
driver/
Code of the driver program
benchmarks/
Benchmark directories.
Each benchmark has its own directory. Different benchmark versions may be
found in different subdirectories.
benchmarkname/
DESCRIPTION
Optional description of the benchmark
src/
Source code of the benchmark
base/
Readable, reference single-threaded CPU-only implementation
cpu/
Optimized single-threaded CPU-only implementation
cuda/
Optimized CUDA implementation
cuda_base/
Slower but more readable CUDA implementation
tools/
Benchmark-specific utilities
compare-output
Tool to verify that the output of a benchmark is correct
datasets/
Benchmark datasets.
Each benchmark has its own directory. Different datasets may be found in
different subdirectories.
benchmarkname/
datasetname/
Directory for a single dataset
input/
Benchmark input files for this dataset.
DESCRIPTION
Optional description of the data set. See README.benchmarks for
using this file to control the passing of command-line parameters
to the benchmark executable.
output/
Reference output for this dataset. The driver only supports a
single file in this directory, which is compared with generated
benchmark output to validate it.
parboil
The driver program for inspecting, compiling, and running benchmarks.
hpvm/test/parboil/README deleted 100644 → 0
+ 0
− 78
View file @ 71fe249e
(c) 2007-2011 The Board of Trustees of the University of Illinois.
This software is distributed under the Illinois Open Source License agreement.
The LICENSE file contains a copy of the license agreement.
Introduction
------------
The Parboil suite was developed from a collection of benchmarks used at the
University of Illinois to measure and compare the performance of
computation-intensive algorithms executing on either a CPU or a GPU. Each
implementation of a GPU algorithm is either in CUDA or OpenCL, and requires
a system capable of executing applications using those APIs.
Quick setup guide
-----------------
To use the parboil benchmark suite:
Create a 'benchmarks' subdirectory (you can also use a symbolic link) and put
benchmarks in it. There should be one subdirectory for each benchmark. We
distribute some benchmarks as a separate archive file. See the
README.benchmarks file for information about the expected format of each
benchmark directory.
Create a 'datasets' subdirectory (you can also use a symbolic link) and put
datasets in it. There should be one subdirectory for each benchmark. We
distribute some datasets as a separate archive file.
There are a number of files that may not be automatically marked executable
after unpacking. Ensure that they are executable by running 'chmod u+x'
with the filename as its argument. If your shell is bash, the following
will work:
chmod u+x ./parboil
chmod u+x benchmarks/*/tools/compare-output
Create a Makefile.conf file in parboil/common to set a few system-specific
paths. You can use some of the examples in that directory as a place to start.
Type './parboil help' to display the driver commands. You can get help on
a particular comand X with './parboil help X'.
Run './parboil' with options to do stuff.
Running a benchmark
-------------------
You can see a list of benchmarks, and the available versions of each
benchmark, with the command
./parboil list
Suppose you want to compile and run the CUDA version of the benchmark
"cutcp". Then the following commands will do this:
./parboil compile cutcp cuda
./parboil run cutcp cuda default
Timing information is recorded with a combination of standard system timers
and CUDA API event timers. Each benchmark should display timer values
following this format:
IO: (seconds spent interacting with the file system)
Kernel: (seconds spent doing device computation, measured asynchronously)
Copy: (seconds CPU spent synchronously copying data to/from the device memory)
Driver: (seconds of CPU time spent sending commands to the device driver)
Compute: (seconds of CPU time spent in computation)
Copy Async: (seconds duration of asynchronous copies to/from the device memory)
CPU/Kernel Overlap: (seconds double-counted by asynchronous and CPU timers)
The driver prints "Pass" if the benchmark's output appears to be correct (i.e.
the compare-output script has an exit code of zero)
hpvm/test/parboil/config deleted 100644 → 0
+ 0
− 36
View file @ 71fe249e
configs = [
('spmv', { 'VERSION' : ["opencl_nvidia_large", "opencl_cpu_large"],
'TEST' : [("large", 10)]
}
)
,('spmv', { 'VERSION' : ["opencl_nvidia_huge", "opencl_cpu_huge"],
'TEST' : [("huge", 3)]
}
)
,('sgemm', { 'VERSION' : ["opencl_opt_8_medium", "opencl_cpu_medium"],
'TEST' : [("medium", 10)]
}
)
,('sgemm', { 'VERSION' : ["opencl_opt_8_4K", "opencl_cpu_4K"],
'TEST' : [("4K", 3)]
}
)
,('lbm', { 'VERSION' : ["opencl_nvidia_short", "opencl_cpu_short"],
'TEST' : [("short", 5)]
}
)
,('lbm', { 'VERSION' : ["opencl_nvidia_long", "opencl_cpu_long"],
'TEST' : [("long", 3)]
}
)
,('stencil', { 'VERSION' : ["opencl_base_default", "opencl_cpu_default"],
'TEST' : [("default", 10)]
}
)
,('stencil', { 'VERSION' : ["opencl_base_large", "opencl_cpu_large"],
'TEST' : [("large", 5)]
}
)
]
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment