Wireless Tests - Intel Atom C2000 Getting Started Manual

Table of Contents

Advertisement

Running Sample Applications
Note: If the signOfLife parameter is not specified, the full run of tests can take several hours to
complete. In addition, for RSA 4096 and DH 4096 tests, there can be up to an hour with no perceived
result activity.
Kernel Space
After building the sample code, the kernel space kernel driver, the user space application, and
the memory mapping driver are located at:
$ICP_ROOT/quickassist/lookaside/access_layer/sample_code/build
To execute the sign of life test in Kernel space, use the following commands:
# cd
$ICP_ROOT/quickassist/lookaside/access_layer/src/sample_code/build #
insmod ./cpa_sample_code.ko signOfLife=1
Note: This test takes a few minutes to complete. When the insmod command is executed, there is no
indication on the terminal window of the activities.
Instructions on viewing the results are included in
Note: If loading of the module fails and some messages in /var/log/messages show Device 0 not
found or not stated or There are no crypto instances, ensure that the kernel option intel_iommu=off
has been configured as a kernel boot parameter, as may be required for older Linux* distributions.
User Space
After building the sample code with the installation script, the kernel space kernel driver, the
user space application, and the memory mapping driver are located at:
$ICP_ROOT/quickassist/lookaside/access_layer/sample_code/build
To execute the sign of life test in User space, use the following commands:
Install the kernel memory driver qaeMemDrv.ko, if the module has not already been installed.
# insmod
$ICP_ROOT/quickassist/lookaside/access_layer/src/sample_code/build/
qaeMemDrv.ko
# cd
$ICP_ROOT/quickassist/lookaside/access_layer/src/sample_code/build #
./cpa_sample_code signOfLife=1
Note: You will observe that execution time of the user space code takes longer than the kernel space
code. This is due to the sample code kernel space memory management driver (qaeMemDrv.ko),
which is slow to allocate and map memory to user space. Before beginning performance
measurements, the sample code allocates memory up-front which slows execution time. This does
not affect the performance of the acceleration driver itself. The acceleration driver user space and
kernel space performance are equivalent, other things being equal (for instance, no throttling takes
place in either case).
10.1.2.2

Wireless Tests

Note: The Wireless tests are supported in user space only. They are not supported in kernel space.
Getting Started Guide
Section 10.1.3, "Test Results"
.
71

Advertisement

Table of Contents
loading

Table of Contents