2.4.1. RT-linux Performance Guide

Read This First

All performance numbers provided in this document are gathered using following Evaluation Modules unless otherwise specified.

Name Description
AM64x EVM AM64x Evaluation Module rev E1 with ARM running at 1GHz, DDRdata rate 1600 MT/S

Table: Evaluation Modules

About This Manual

This document provides performance data for each of the device drivers which are part of the Process SDK Linux package. This document should be used in conjunction with release notes and user guides provided with the Process SDK Linux package for information on specific issues present with drivers included in a particular release.

If You Need Assistance

For further information or to report any problems, contact http://e2e.ti.com/ or http://support.ti.com/ System Benchmarks LMBench

LMBench is a collection of microbenchmarks of which the memory bandwidth and latency related ones are typically used to estimate processor memory system performance.

Latency: lat_mem_rd-stride128-szN, where N is equal to or smaller than the cache size at given level measures the cache miss penalty. N that is at least double the size of last level cache is the latency to external memory.

Bandwidth: bw_mem_bcopy-N, where N is is equal to or smaller than the cache size at a given level measures the achivable memory bandwidth from software doing a memcpy() type operation. Typical use is for external memory bandwidth calculation. The bandwidth is calculated as byte read and written counts as 1 which should be roughly half of STREAM copy result.

Benchmarks am64xx-evm: perf
af_unix_sock_stream_latency (microsec) 51.25
af_unix_socket_stream_bandwidth (MB/s) 726.10
bw_file_rd-io-1mb (MB/s) 833.75
bw_file_rd-o2c-1mb (MB/s) 495.70
bw_mem-bcopy-16mb (MB/s) 868.81
bw_mem-bcopy-1mb (MB/s) 915.75
bw_mem-bcopy-2mb (MB/s) 898.07
bw_mem-bcopy-4mb (MB/s) 911.68
bw_mem-bcopy-8mb (MB/s) 923.25
bw_mem-bzero-16mb (MB/s) 2125.40
bw_mem-bzero-1mb (MB/s) 1520.77 (min 915.75, max 2125.78)
bw_mem-bzero-2mb (MB/s) 1507.24 (min 898.07, max 2116.40)
bw_mem-bzero-4mb (MB/s) 1517.79 (min 911.68, max 2123.89)
bw_mem-bzero-8mb (MB/s) 1524.04 (min 923.25, max 2124.83)
bw_mem-cp-16mb (MB/s) 522.21
bw_mem-cp-1mb (MB/s) 1523.89 (min 574.71, max 2473.06)
bw_mem-cp-2mb (MB/s) 1368.88 (min 551.57, max 2186.19)
bw_mem-cp-4mb (MB/s) 1345.86 (min 532.27, max 2159.44)
bw_mem-cp-8mb (MB/s) 1373.59 (min 606.43, max 2140.75)
bw_mem-fcp-16mb (MB/s) 811.11
bw_mem-fcp-1mb (MB/s) 1489.15 (min 852.51, max 2125.78)
bw_mem-fcp-2mb (MB/s) 1491.98 (min 867.55, max 2116.40)
bw_mem-fcp-4mb (MB/s) 1477.58 (min 831.26, max 2123.89)
bw_mem-fcp-8mb (MB/s) 1521.24 (min 917.64, max 2124.83)
bw_mem-frd-16mb (MB/s) 1267.43
bw_mem-frd-1mb (MB/s) 1099.21 (min 852.51, max 1345.90)
bw_mem-frd-2mb (MB/s) 1080.82 (min 867.55, max 1294.08)
bw_mem-frd-4mb (MB/s) 1076.13 (min 831.26, max 1321.00)
bw_mem-frd-8mb (MB/s) 1153.63 (min 917.64, max 1389.61)
bw_mem-fwr-16mb (MB/s) 2136.18
bw_mem-fwr-1mb (MB/s) 1909.48 (min 1345.90, max 2473.06)
bw_mem-fwr-2mb (MB/s) 1740.14 (min 1294.08, max 2186.19)
bw_mem-fwr-4mb (MB/s) 1740.22 (min 1321.00, max 2159.44)
bw_mem-fwr-8mb (MB/s) 1765.18 (min 1389.61, max 2140.75)
bw_mem-rd-16mb (MB/s) 1386.60
bw_mem-rd-1mb (MB/s) 1166.48 (min 932.14, max 1400.81)
bw_mem-rd-2mb (MB/s) 1136.15 (min 878.09, max 1394.21)
bw_mem-rd-4mb (MB/s) 1143.20 (min 887.31, max 1399.09)
bw_mem-rd-8mb (MB/s) 1161.72 (min 926.78, max 1396.65)
bw_mem-rdwr-16mb (MB/s) 917.27
bw_mem-rdwr-1mb (MB/s) 729.60 (min 574.71, max 884.49)
bw_mem-rdwr-2mb (MB/s) 692.34 (min 551.57, max 833.10)
bw_mem-rdwr-4mb (MB/s) 686.79 (min 532.27, max 841.31)
bw_mem-rdwr-8mb (MB/s) 719.49 (min 606.43, max 832.55)
bw_mem-wr-16mb (MB/s) 945.18
bw_mem-wr-1mb (MB/s) 908.32 (min 884.49, max 932.14)
bw_mem-wr-2mb (MB/s) 855.60 (min 833.10, max 878.09)
bw_mem-wr-4mb (MB/s) 864.31 (min 841.31, max 887.31)
bw_mem-wr-8mb (MB/s) 879.67 (min 832.55, max 926.78)
bw_mmap_rd-mo-1mb (MB/s) 1246.44
bw_mmap_rd-o2c-1mb (MB/s) 464.83
bw_pipe (MB/s) 268.03
bw_unix (MB/s) 726.10
lat_connect (us) 90.68
lat_ctx-2-128k (us) 8.77
lat_ctx-2-256k (us) 23.90
lat_ctx-4-128k (us) 9.32
lat_ctx-4-256k (us) 7.57
lat_fs-0k (num_files) 159.00
lat_fs-10k (num_files) 74.00
lat_fs-1k (num_files) 101.00
lat_fs-4k (num_files) 108.00
lat_mem_rd-stride128-sz1000k (ns) 46.80
lat_mem_rd-stride128-sz125k (ns) 7.78
lat_mem_rd-stride128-sz250k (ns) 15.67
lat_mem_rd-stride128-sz31k (ns) 5.11
lat_mem_rd-stride128-sz50 (ns) 3.01
lat_mem_rd-stride128-sz500k (ns) 43.31
lat_mem_rd-stride128-sz62k (ns) 7.29
lat_mmap-1m (us) 74.00
lat_ops-double-add (ns) 0.73
lat_ops-double-mul (ns) 4.03
lat_ops-float-add (ns) 0.73
lat_ops-float-mul (ns) 4.04
lat_ops-int-add (ns) 1.01
lat_ops-int-bit (ns) 0.67
lat_ops-int-div (ns) 6.06
lat_ops-int-mod (ns) 6.38
lat_ops-int-mul (ns) 3.05
lat_ops-int64-add (ns) 1.01
lat_ops-int64-bit (ns) 0.67
lat_ops-int64-div (ns) 9.54
lat_ops-int64-mod (ns) 7.36
lat_pagefault (us) 1.85
lat_pipe (us) 26.60
lat_proc-exec (us) 1909.33
lat_proc-fork (us) 1576.00
lat_proc-proccall (us) 0.01
lat_select (us) 42.20
lat_sem (us) 3.93
lat_sig-catch (us) 7.95
lat_sig-install (us) 0.82
lat_sig-prot (us) 0.39
lat_syscall-fstat (us) 1.94
lat_syscall-null (us) 0.40
lat_syscall-open (us) 407.71
lat_syscall-read (us) 0.77
lat_syscall-stat (us) 5.32
lat_syscall-write (us) 0.65
lat_tcp (us) 0.80
lat_unix (us) 51.25
latency_for_0.50_mb_block_size (nanosec) 43.31
latency_for_1.00_mb_block_size (nanosec) 23.40 (min 0.00, max 46.80)
pipe_bandwidth (MBs) 268.03
pipe_latency (microsec) 26.60
procedure_call (microsec) 0.01
select_on_200_tcp_fds (microsec) 42.20
semaphore_latency (microsec) 3.93
signal_handler_latency (microsec) 0.82
signal_handler_overhead (microsec) 7.95
tcp_ip_connection_cost_to_localhost (microsec) 90.68
tcp_latency_using_localhost (microsec) 0.80

Table: LM Bench Metrics Dhrystone

Dhrystone is a core only benchmark that runs from warm L1 caches in all modern processors. It scales linearly with clock speed. For standard ARM cores the DMIPS/MHz score will be identical with the same compiler and flags.

Benchmarks am64xx-evm: perf
cpu_clock (MHz) 400.00
dhrystone_per_mhz (DMIPS/MHz) 7.30
dhrystone_per_second (DhrystoneP) 5128205.00

Table: Dhrystone Benchmark Whetstone

Benchmarks am64xx-evm: perf
whetstone (MIPS) 3333.30

Table: Whetstone Benchmark Linpack

Linpack measures peak double precision (64 bit) floating point performance in sloving a dense linear system.

Benchmarks am64xx-evm: perf
linpack (Kflops) 396230.00

Table: Linpack Benchmark NBench

Benchmarks am64xx-evm: perf
assignment (Iterations) 9.75
fourier (Iterations) 16243.00
fp_emulation (Iterations) 76.56
huffman (Iterations) 837.98
idea (Iterations) 2452.10
lu_decomposition (Iterations) 390.58
neural_net (Iterations) 5.60
numeric_sort (Iterations) 360.40
string_sort (Iterations) 118.45

Table: NBench Benchmarks Stream

STREAM is a microbenchmarks for measuring data memory system performance without any data reuse. It is designed to miss on caches and exercise data prefetcher and apeculative accesseses. it uses double precision floating point (64bit) but in most modern processors the memory access will be the bottleck. The four individual scores are copy, scale as in multiply by constant, add two numbers, and triad for multiply accumulate. For bandwidth a byte read counts as one and a byte written counts as one resulting in a score that is double the bandwidth LMBench will show.

Benchmarks am64xx-evm: perf
add (MB/s) 1690.80
copy (MB/s) 1955.60
scale (MB/s) 2326.70
triad (MB/s) 1693.50

Table: Stream CoreMarkPro

CoreMark®-Pro is a comprehensive, advanced processor benchmark that works with and enhances the market-proven industry-standard EEMBC CoreMark® benchmark. While CoreMark stresses the CPU pipeline, CoreMark-Pro tests the entire processor, adding comprehensive support for multicore technology, a combination of integer and floating-point workloads, and data sets for utilizing larger memory subsystems.

Table 2.1 :header: “Benchmarks”,”am64xx-evm: perf”
cjpeg-rose7-preset (workloads/) 29.85
core (workloads/) 0.21
coremark-pro () 582.00
linear_alg-mid-100x100-sp (workloads/) 10.45
loops-all-mid-10k-sp (workloads/) 0.49
nnet_test (workloads/) 0.78
parser-125k (workloads/) 4.95
radix2-big-64k (workloads/) 19.39
sha-test (workloads/) 57.80
zip-test (workloads/) 15.63

Table: CoreMarkPro

Table 2.2 :header: “Benchmarks”,”am64xx-evm: perf”
cjpeg-rose7-preset (workloads/) 57.14
core (workloads/) 0.43
coremark-pro () 1070.90
linear_alg-mid-100x100-sp (workloads/) 20.54
loops-all-mid-10k-sp (workloads/) 0.89
nnet_test (workloads/) 1.55
parser-125k (workloads/) 6.56
radix2-big-64k (workloads/) 34.47
sha-test (workloads/) 114.94
zip-test (workloads/) 28.99

Table: CoreMarkPro for Two Cores MultiBench

MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and demonstrating a processor’s support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, demonstrating concurrency over both code and data. MultiBench combines a wide variety of application-specific workloads with the EEMBC Multi-Instance-Test Harness (MITH), compatible and portable with most any multicore processors and operating systems. MITH uses a thread-based API (POSIX-compliant) to establish a common programming model that communicates with the benchmark through an abstraction layer and provides a flexible interface to allow a wide variety of thread-enabled workloads to be tested.

Table 2.3 :header: “Benchmarks”,”am64xx-evm: perf”
4m-check (workloads/) 322.21
4m-check-reassembly (workloads/) 62.66
4m-check-reassembly-tcp (workloads/) 37.99
4m-check-reassembly-tcp-cmykw2-rotatew2 (workloads/) 15.42
4m-check-reassembly-tcp-x264w2 (workloads/) 0.76
4m-cmykw2 (workloads/) 87.72
4m-cmykw2-rotatew2 (workloads/) 18.09
4m-reassembly (workloads/) 52.00
4m-rotatew2 (workloads/) 25.13
4m-tcp-mixed (workloads/) 84.66
4m-x264w2 (workloads/) 0.77
empty-wld (workloads/) 1.00
idct-4m (workloads/) 13.69
idct-4mw1 (workloads/) 13.70
ippktcheck-4m (workloads/) 323.16
ippktcheck-4mw1 (workloads/) 322.46
ipres-4m (workloads/) 67.75
ipres-4mw1 (workloads/) 69.00
md5-4m (workloads/) 18.68
md5-4mw1 (workloads/) 18.86
rgbcmyk-4m (workloads/) 44.73
rgbcmyk-4mw1 (workloads/) 44.63
rotate-4ms1 (workloads/) 17.12
rotate-4ms1w1 (workloads/) 17.23
rotate-4ms64 (workloads/) 17.32
rotate-4ms64w1 (workloads/) 17.33
x264-4mq (workloads/) 0.41
x264-4mqw1 (workloads/) 0.41

Table: Multibench Spec2K6

CPU2006 is a set of benchmarks designed to test the CPU performance of a modern server computer system. It is split into two components, the first being CINT2006, the other being CFP2006 (SPECfp), for floating point testing.

SPEC defines a base runtime for each of the 12 benchmark programs. For SPECint2006, that number ranges from 1000 to 3000 seconds. The timed test is run on the system, and the time of the test system is compared to the reference time, and a ratio is computed. That ratio becomes the SPECint score for that test. (This differs from the rating in SPECINT2000, which multiplies the ratio by 100.)

As an example for SPECint2006, consider a processor which can run 400.perlbench in 2000 seconds. The time it takes the reference machine to run the benchmark is 9770 seconds. Thus the ratio is 4.885. Each ratio is computed, and then the geometric mean of those ratios is computed to produce an overall value.

Rate (Multiple Cores)

Table: Spec2K6

Speed (Single Core)

Table: Spec2K6 Speed Maximum Latency under different use cases Shield (dedicated core) Case

The following tests measure worst-case latency under different scenarios or use cases.
Cyclictest application was used to measured latency. Each test ran for 4 hours.
Two cgroups were used using shield_shell procedure shown below.
The application running the use case and cyclictest ran on a dedicated cpu (rt) while the rest of threads ran on nonrt cpu.
create_cgroup nonrt 0
create_cgroup rt 1
for pid in $(cat /sys/fs/cgroup/tasks); do /bin/echo $pid > /sys/fs/cgroup/nonrt/tasks; done
/bin/echo $$ > /sys/fs/cgroup/rt/tasks

Benchmarks Core #1 (nonrt) Core#2 (rt)
Min Latencies 6 6
Avg Latencies 8 8
Max Latencies 92 72

Table: Cyclic test for Two Cores Boot-time Measurement Boot media: MMCSD

Boot Configuration am64xx-evm: boot time (sec)
Kernel boot time test when bootloader, kernel and sdk-rootfs are in mmc-sd 28.74 (min 27.17, max 32.35)
Kernel boot time test when init is /bin/sh and bootloader, kernel and sdk-rootfs are in mmc-sd 3.43 (min 3.42, max 3.47)

Table: Boot time MMC/SD Ethernet

Ethernet performance benchmarks were measured using Netperf 2.7.1 https://hewlettpackard.github.io/netperf/doc/netperf.html Test procedures were modeled after those defined in RFC-2544: https://tools.ietf.org/html/rfc2544, where the DUT is the TI device and the “tester” used was a Linux PC. To produce consistent results, it is recommended to carry out performance tests in a private network and to avoid running NFS on the same interface used in the test. In these results, CPU utilization was captured as the total percentage used across all cores on the device, while running the performance test over one external interface.

UDP Throughput (0% loss) was measured by the procedure defined in RFC-2544 section 26.1: Throughput. In this scenario, netperf options burst_size (-b) and wait_time (-w) are used to limit bandwidth during different trials of the test, with the goal of finding the highest rate at which no loss is seen. For example, to limit bandwidth to 500Mbits/sec with 1472B datagram:

burst_size = <bandwidth (bits/sec)> / 8 (bits -> bytes) / <UDP datagram size> / 100 (seconds -> 10 ms)
burst_size = 500000000 / 8 / 1472 / 100 = 425

wait_time = 10 milliseconds (minimum supported by Linux PC used for testing)

UDP Throughput (possible loss) was measured by capturing throughput and packet loss statistics when running the netperf test with no bandwidth limit (remove -b/-w options).

In order to start a netperf client on one device, the other device must have netserver running. To start netserver:

netserver [-p <port_number>] [-4 (IPv4 addressing)] [-6 (IPv6 addressing)]

Running the following shell script from the DUT will trigger netperf clients to measure bidirectional TCP performance for 60 seconds and report CPU utilization. Parameter -k is used in client commands to summarize selected statistics on their own line and -j is used to gain additional timing measurements during the test.

for i in 1
   netperf -H <tester ip> -j -c -l 60 -t TCP_STREAM --

   netperf -H <tester ip> -j -c -l 60 -t TCP_MAERTS --

Running the following commands will trigger netperf clients to measure UDP burst performance for 60 seconds at various burst/datagram sizes and report CPU utilization.

  • For UDP egress tests, run netperf client from DUT and start netserver on tester.
netperf -H <tester ip> -j -c -l 60 -t UDP_STREAM -b <burst_size> -w <wait_time> -- -m <UDP datagram size>
  • For UDP ingress tests, run netperf client from tester and start netserver on DUT.
netperf -H <DUT ip> -j -C -l 60 -t UDP_STREAM -b <burst_size> -w <wait_time> -- -m <UDP datagram size>

TCP Bidirectional Throughput

Command Used am64xx-evm: THROUGHPUT (Mbits/sec) am64xx-evm: CPU Load % (LOCAL_CPU_UTIL)
netperf -H -j -c -C -l 60 -t TCP_STREAM; netperf -H -j -c -C -l 60 -t TCP_MAERTS 1004.34 97.86

Table: CPSW TCP Bidirectional Throughput

UDP Throughput

Frame Size(bytes) am64xx-evm: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) am64xx-evm: THROUGHPUT (Mbits/sec) am64xx-evm: CPU Load % (LOCAL_CPU_UTIL)
64 18.00 7.47 87.20
128 82.00 33.10 86.56
256 210.00 84.16 86.45
512 466.00 264.81 49.04
1024 978.00 373.49 84.69
1518 1472.00 554.49 84.63

Table: CPSW UDP Egress Throughput

Frame Size(bytes) am64xx-evm: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) am64xx-evm: THROUGHPUT (Mbits/sec) am64xx-evm: CPU Load % (LOCAL_CPU_UTIL)
64 18.00 1.05 3.68
128 82.00 5.90 4.12
256 210.00 16.97 16.92
512 466.00 49.95 7.06
1024 978.00 80.59 18.04
1518 1472.00 122.46 6.78

Table: CPSW UDP Ingress Throughput

Frame Size(bytes) am64xx-evm: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) am64xx-evm: THROUGHPUT (Mbits/sec) am64xx-evm: CPU Load % (LOCAL_CPU_UTIL) am64xx-evm: Packet Loss %
64 18.00 16.75 39.08 48.26
128 82.00 67.31 56.35 70.71
256 210.00 165.79 55.32 53.79
512 466.00 397.44 39.76 50.34
1024 978.00 639.22 52.44 31.65
1518 1472.00 868.78 64.40 9.13

Table: CPSW UDP Ingress Throughput (possible loss) PCIe Driver PCIe-NVMe-SSD

Table 2.4 :header: “Buffer size (bytes)”,”am64xx-evm: Write EXT4 Throughput (Mbytes/sec)”,”am64xx-evm: Write EXT4 CPU Load (%)”,”am64xx-evm: Read EXT4 Throughput (Mbytes/sec)”,”am64xx-evm: Read EXT4 CPU Load (%)”
1m 363.00 19.88 398.00 15.30
4m 360.00 16.75 398.00 13.50
4k 64.90 52.04 82.20 49.69
256k 374.00 25.95 397.00 16.77
  • Filesize used is: 10G
  • FIO command options: –ioengine=libaio –iodepth=4 –numjobs=1 –direct=1 –runtime=60 –time_based
  • Platform: Speed 8GT/s, Width x1
  • SSD being used: Lite-On Technology Corporation M8Pe Series NVMe SSD [14a4:22f1] (rev 01) OSPI Flash Driver UBIFS

Buffer size (bytes) am64xx-evm: Write UBIFS Throughput (Mbytes/sec) am64xx-evm: Write UBIFS CPU Load (%) am64xx-evm: Read UBIFS Throughput (Mbytes/sec) am64xx-evm: Read UBIFS CPU Load (%)
102400 0.18 (min 0.12, max 0.29) 54.67 (min 54.31, max 54.92) 44.95 60.00
262144 0.14 (min 0.10, max 0.18) 54.16 (min 53.83, max 54.53) 45.34 50.00
524288 0.14 (min 0.10, max 0.18) 54.40 (min 53.92, max 54.92) 47.01 44.44
1048576 0.14 (min 0.10, max 0.18) 54.19 (min 53.58, max 54.61) 43.81 44.44 RAW

File size (Mbytes) am64xx-evm: Raw Read Throughput (Mbytes/sec)
50 131.58 EMMC Driver


IMPORTANT: The performance numbers can be severely affected if the media is mounted in sync mode. Hot plug scripts in the filesystem mount removable media in sync mode to ensure data integrity. For performance sensitive applications, umount the auto-mounted filesystem and re-mount in async mode.

Buffer size (bytes) am64xx-evm: Write EXT4 Throughput (Mbytes/sec) am64xx-evm: Write EXT4 CPU Load (%) am64xx-evm: Read EXT4 Throughput (Mbytes/sec) am64xx-evm: Read EXT4 CPU Load (%)
1m 58.60 4.69 313.00 14.37
4m 58.90 3.17 312.00 11.71
4k 41.80 53.05 54.60 65.23
256k 59.20 6.95 313.00 18.62 MMC/SD Driver


IMPORTANT: The performance numbers can be severely affected if the media is mounted in sync mode. Hot plug scripts in the filesystem mount removable media in sync mode to ensure data integrity. For performance sensitive applications, umount the auto-mounted filesystem and re-mount in async mode.

Buffer size (bytes) am64xx-evm: Write EXT4 Throughput (Mbytes/sec) am64xx-evm: Write EXT4 CPU Load (%) am64xx-evm: Read EXT4 Throughput (Mbytes/sec) am64xx-evm: Read EXT4 CPU Load (%)
1m 19.80 2.46 87.50 5.23
4m 18.50 2.10 84.50 3.96
4k 4.95 11.61 16.70 20.55
256k 19.00 3.41 85.30 6.76

The performance numbers were captured using the following:

  • SanDisk 8GB MicroSDHC Class 10 Memory Card
  • Partition was mounted with async option USB Driver USB Host Controller


IMPORTANT: For Mass-storage applications, the performance numbers can be severely affected if the media is mounted in sync mode. Hot plug scripts in the filesystem mount removable media in sync mode to ensure data integrity. For performance sensitive applications, umount the auto-mounted filesystem and re-mount in async mode.

Setup : SAMSUNG 850 PRO 2.5” 128GB SATA III Internal Solid State Drive (SSD) used with Inateck ASM1153E enclosure is connected to usb port under test. File read/write performance data is captured.

Buffer size (bytes) am64xx-evm: Write EXT4 Throughput (Mbytes/sec) am64xx-evm: Write EXT4 CPU Load (%) am64xx-evm: Read EXT4 Throughput (Mbytes/sec) am64xx-evm: Read EXT4 CPU Load (%)
1m 37.00 8.03 37.40 7.27
4m 37.70 7.39 37.80 6.79
4k 15.20 35.51 16.20 32.52
256k 35.30 10.20 36.40 11.06 USB Device Controller


Number of Blocks am64xx-evm: Throughput (MB/sec)
150 39.30


Number of Blocks am64xx-evm: Throughput (MB/sec)
150 25.50 CRYPTO Driver OpenSSL Performance

Listed for each algorithm are the code snippets used to run each benchmark test.

time -v openssl speed -elapsed -evp aes-128-cbc IPSec Hardware Performance

Note: queue_len is set to 300 and software fallback threshold set to 9 to enable software support for optimal performance IPSec Software Performance

Algorithm am64xx-evm: Throughput (Mbps) am64xx-evm: Packets/Sec am64xx-evm: CPU Load
3des 51.20 4.00 50.33
aes256 4.20 0.00 31.81