Optimizing data plane performance with the Intel vRAN Dedicated Accelerator ACC100

    The vRAN Dedicated Accelerator ACC100, based on Intel eASIC technology is designed to offload and accelerate the computing-intensive process of forward error correction (FEC) for 4G/LTE and 5G technology, freeing up processing power. Intel eASIC devices are structured ASICs, an intermediate technology between FPGAs and standard application-specific integrated circuits (ASICs).

    Intel vRAN Dedicated Accelerator ACC100 support on OKD uses one Operator:

    • OpenNESS Operator for Wireless FEC Accelerators

    The role of the OpenNESS Operator for Intel Wireless forward error correction (FEC) Accelerator is to orchestrate and manage the devices exposed by a range of Intel vRAN FEC acceleration hardware within the OKD cluster.

    One of the most compute-intensive 4G/LTE and 5G workloads is RAN layer 1 (L1) FEC. FEC resolves data transmission errors over unreliable or noisy communication channels. FEC technology detects and corrects a limited number of errors in 4G/LTE or 5G data without the need for retransmission.

    The FEC device provided by the Intel vRAN Dedicated Accelerator ACC100 supports the vRAN use case.

    The OpenNESS SR-IOV Operator for Wireless FEC Accelerators provides functionality to create virtual functions (VFs) for the FEC device, binds them to appropriate drivers, and configures the VFs queues for functionality in 4G/LTE or 5G deployment.

    As a cluster administrator, you can install the OpenNESS SR-IOV Operator for Wireless FEC Accelerators by using the OKD CLI or the web console.

    As a cluster administrator, you can install the OpenNESS SR-IOV Operator for Wireless FEC Accelerators by using the CLI.

    Prerequisites

    • A cluster installed on bare-metal hardware.

    • Install the OpenShift CLI ().

    • Log in as a user with cluster-admin privileges.

    Procedure

    1. Create a namespace for the OpenNESS SR-IOV Operator for Wireless FEC Accelerators by completing the following actions:

      1. Define the vran-acceleration-operators namespace by creating a file named sriov-namespace.yaml as shown in the following example:

      2. Create the namespace by running the following command:

        1. $ oc create -f sriov-namespace.yaml

    2. Install the OpenNESS SR-IOV Operator for Wireless FEC Accelerators in the namespace you created in the previous step by creating the following objects:

      1. Create the following OperatorGroup custom resource (CR) and save the YAML in the sriov-operatorgroup.yaml file:

        1. apiVersion: operators.coreos.com/v1
        2. kind: OperatorGroup
        3. metadata:
        4.     name: vran-operators
        5.     namespace: vran-acceleration-operators
        6. spec:
        7.     targetNamespaces:
        8.       - vran-acceleration-operators

      2. Create the OperatorGroup CR by running the following command:

        1. $ oc create -f sriov-operatorgroup.yaml

      3. Run the following command to get the channel value required for the next step.

        1. $ oc get packagemanifest sriov-fec -n openshift-marketplace -o jsonpath='{.status.defaultChannel}'

        Example output

        1. stable

      4. Create the following Subscription CR and save the YAML in the sriov-sub.yaml file:

        1. apiVersion: operators.coreos.com/v1alpha1
        2. kind: Subscription
        3. metadata:
        4.     name: sriov-fec-subscription
        5.     namespace: vran-acceleration-operators
        6. spec:
        7.     channel: "<channel>" (1)
        8.     name: sriov-fec
        9.     source: certified-operators (2)
        10.     sourceNamespace: openshift-marketplace

      5. Create the Subscription CR by running the following command:

        1. $ oc create -f sriov-sub.yaml

    Verification

    • Verify that the Operator is installed:

      1. $ oc get csv -n vran-acceleration-operators -o custom-columns=Name:.metadata.name,Phase:.status.phase

      Example output

      1. Name                                        Phase
      2. sriov-fec.v1.1.0                            Succeeded

    As a cluster administrator, you can install the OpenNESS SR-IOV Operator for Wireless FEC Accelerators by using the web console.

    You must create the Namespace and OperatorGroup custom resource (CR) as mentioned in the previous section.

    Procedure

    1. Install the OpenNESS SR-IOV Operator for Wireless FEC Accelerators by using the OKD web console:

      1. In the OKD web console, click Operators → OperatorHub.

      2. Choose OpenNESS SR-IOV Operator for Wireless FEC Accelerators from the list of available Operators, and then click Install.

      3. On the Install Operator page, select All namespaces on the cluster. Then, click Install.

    2. Optional: Verify that the SRIOV-FEC Operator is installed successfully:

      1. Switch to the Operators → Installed Operators page.

      2. Ensure that OpenNESS SR-IOV Operator for Wireless FEC Accelerators is listed in the vran-acceleration-operators project with a Status of InstallSucceeded.

        During installation an Operator might display a Failed status. If the installation later succeeds with an InstallSucceeded message, you can ignore the Failed message.

        • Go to the Operators → Installed Operators page and inspect the Operator Subscriptions and Install Plans tabs for any failure or errors under Status.

        • Go to the Workloads → Pods page and check the logs for pods in the vran-acceleration-operators project.

    Programming the Intel vRAN Dedicated Accelerator ACC100 exposes the Single Root I/O Virtualization (SRIOV) virtual function (VF) devices that are then used to accelerate the forward error correction (FEC) in the vRAN workload. The Intel vRAN Dedicated Accelerator ACC100 accelerates 4G and 5G Virtualized Radio Access Networks (vRAN) workloads. This in turn increases the overall compute capacity of a commercial, off-the-shelf platform. This device is also known as Mount Bryce.

    The SR-IOV-FEC Operator handles the management of the FEC devices that are used to accelerate the FEC process in vRAN L1 applications.

    Configuring the SR-IOV-FEC Operator involves:

    • Creating the virtual functions (VFs) for the FEC device

    • Binding the VFs to the appropriate drivers

    • Configuring the VF queues for desired functionality in a 4G or 5G deployment

    The role of forward error correction (FEC) is to correct transmission errors, where certain bits in a message can be lost or garbled. Messages can be lost or garbled due to noise in the transmission media, interference, or low signal strength. Without FEC, a garbled message would have to be resent, adding to the network load and impacting throughput and latency.

    Prerequisites

    • Intel FPGA ACC100 5G/4G card.

    • Node or nodes installed with the OpenNESS Operator for Wireless FEC Accelerators.

    • Enable global SR-IOV and VT-d settings in the BIOS for the node.

    • RT kernel configured with Performance Addon Operator.

    • Log in as a user with cluster-admin privileges.

    Procedure

    1. Change to the vran-acceleration-operators project:

      1. $ oc project vran-acceleration-operators

    2. Verify that the SR-IOV-FEC Operator is installed:

      1. $ oc get csv -o custom-columns=Name:.metadata.name,Phase:.status.phase

      Example output

      1. Name                                        Phase
      2. sriov-fec.v1.1.0                            Succeeded

    3. Verify that the sriov-fec pods are running:

      1. $  oc get pods

      Example output

      • sriov-device-plugin expose the FEC virtual functions as resources under the node

      • sriov-fec-controller-manager applies CR to the node and maintains the operands containers

      • sriov-fec-daemonset is responsible for:

        • Discovering the SRIOV NICs on each node.

        • Syncing the status of the custom resource (CR) defined in step 6.

        • Taking the spec of the CR as input and configuring the discovered NICs.

    1. Retrieve all the nodes containing one of the supported vRAN FEC accelerator devices:

      1. $ oc get sriovfecnodeconfig

      Example output

      1. NAME             CONFIGURED
      2. node1            Succeeded

    2. Find the physical function (PF) of the SR-IOV FEC accelerator device to configure:

      1. $ oc get sriovfecnodeconfig node1 -o yaml

      Example output

      1. status:
      2.     conditions:
      3.     - lastTransitionTime: "2021-03-19T17:19:37Z"
      4.       message: Configured successfully
      5.       observedGeneration: 1
      6.       reason: ConfigurationSucceeded
      7.       status: "True"
      8.       type: Configured
      9.     inventory:
      10.        sriovAccelerators:
      11.        - deviceID: 0d5c
      12.          driver: ""
      13.          maxVirtualFunctions: 16
      14.          pciAddress: 0000:af:00.0 (1)
      15.          vendorID: "8086"
      16.          virtualFunctions: [] (2)

    3. Configure the number of virtual functions and queue groups on the FEC device:

      1. Create the following custom resource (CR) and save the YAML in the sriovfec_acc100cr.yaml file:

        This example configures the ACC100 8/8 queue groups for 5G, 4 queue groups for Uplink, and another 4 queue groups for Downlink.

        1. kind: SriovFecClusterConfig
        2. metadata:
        3.   name: config (1)
        4. spec:
        5.   nodes:
        6.    - nodeName: node1 (2)
        7.      physicalFunctions:
        8.        - pciAddress: 0000:af:00.0 (3)
        9.          pfDriver: "pci-pf-stub"
        10.          vfDriver: "vfio-pci"
        11.          vfAmount: 16 (4)
        12.          bbDevConfig:
        13.            acc100:
        14.              # Programming mode: 0 = VF Programming, 1 = PF Programming
        15.              pfMode: false
        16.              numVfBundles: 16
        17.              maxQueueSize: 1024
        19.                numQueueGroups: 0
        20.                numAqsPerGroups: 16
        21.                aqDepthLog2: 4
        22.              downlink4G:
        23.               numQueueGroups: 0
        24.               numAqsPerGroups: 16
        25.               aqDepthLog2: 4
        26.              uplink5G:
        27.               numQueueGroups: 4
        28.               numAqsPerGroups: 16
        29.               aqDepthLog2: 4
        30.              downlink5G:
        31.               numQueueGroups: 4
        32.               numAqsPerGroups: 16
        33.               aqDepthLog2: 4
        1Specify a name for the CR object. The only name that can be specified is config.
        2Specify the node name.
        3Specify the PCI address of the card on which the SR-IOV-FEC Operator will be installed.
        4Specify the number of virtual functions to create. For the Intel vRAN Dedicated Accelerator ACC100, create all 16 VFs.

      2. Apply the CR:

        1. $ oc apply -f sriovfec_acc100cr.yaml

        After applying the CR, the SR-IOV FEC daemon starts configuring the FEC device.

    Verification

    1. Check the status:

      1. $ oc get sriovfecclusterconfig config -o yaml

      Example output

      1. status:
      2.     conditions:
      3.     - lastTransitionTime: "2021-03-19T11:46:22Z"
      4.       message: Configured successfully
      5.       observedGeneration: 1
      6.       reason: Succeeded
      7.       status: "True"
      8.       type: Configured
      9.     inventory:
      10.       sriovAccelerators:
      11.       - deviceID: 0d5c
      12.         driver: pci-pf-stub
      13.         maxVirtualFunctions: 16
      14.         pciAddress: 0000:af:00.0
      15.         vendorID: "8086"
      16.         virtualFunctions:
      17.         - deviceID: 0d5d
      18.           driver: vfio-pci
      19.           pciAddress: 0000:b0:00.0
      20.         - deviceID: 0d5d
      21.           driver: vfio-pci
      22.           pciAddress: 0000:b0:00.1
      23.         - deviceID: 0d5d
      24.           driver: vfio-pci
      25.           pciAddress: 0000:b0:00.2
      26.         - deviceID: 0d5d
      27.           driver: vfio-pci
      28.           pciAddress: 0000:b0:00.3
      29.         - deviceID: 0d5d
      30.           driver: vfio-pci
      31.           pciAddress: 0000:b0:00.4

    2. Check the logs:

      1. Determine the pod name of the SR-IOV daemon:

        1. $ oc get po -o wide | grep sriov-fec-daemonset | grep node1

        Example output

        1. sriov-fec-daemonset-kqqs6                      1/1     Running   0          19h

      2. View the logs:

        1. $ oc logs sriov-fec-daemonset-kqqs6

        Example output

        1. {"level":"Level(-2)","ts":1616794345.4786215,"logger":"daemon.drainhelper.cordonAndDrain()","msg":"node drained"}
        2. {"level":"Level(-4)","ts":1616794345.4786265,"logger":"daemon.drainhelper.Run()","msg":"worker function - start"}
        3. {"level":"Level(-4)","ts":1616794345.5762916,"logger":"daemon.NodeConfigurator.applyConfig","msg":"current node status","inventory":{"sriovAccelerat
        4. ors":[{"vendorID":"8086","deviceID":"0b32","pciAddress":"0000:20:00.0","driver":"","maxVirtualFunctions":1,"virtualFunctions":[]},{"vendorID":"8086"
        5. ,"deviceID":"0d5c","pciAddress":"0000:af:00.0","driver":"","maxVirtualFunctions":16,"virtualFunctions":[]}]}}
        6. {"level":"Level(-4)","ts":1616794345.5763638,"logger":"daemon.NodeConfigurator.applyConfig","msg":"configuring PF","requestedConfig":{"pciAddress":"
        7. 0000:af:00.0","pfDriver":"pci-pf-stub","vfDriver":"vfio-pci","vfAmount":2,"bbDevConfig":{"acc100":{"pfMode":false,"numVfBundles":16,"maxQueueSize":1
        8. 024,"uplink4G":{"numQueueGroups":4,"numAqsPerGroups":16,"aqDepthLog2":4},"downlink4G":{"numQueueGroups":4,"numAqsPerGroups":16,"aqDepthLog2":4},"uplink5G":{"numQueueGroups":0,"numAqsPerGroups":16,"aqDepthLog2":4},"downlink5G":{"numQueueGroups":0,"numAqsPerGroups":16,"aqDepthLog2":4}}}}}
        9. {"level":"Level(-4)","ts":1616794345.5774765,"logger":"daemon.NodeConfigurator.loadModule","msg":"executing command","cmd":"/usr/sbin/chroot /host/ modprobe pci-pf-stub"}
        10. {"level":"Level(-4)","ts":1616794345.5842702,"logger":"daemon.NodeConfigurator.loadModule","msg":"commands output","output":""}
        11. {"level":"Level(-4)","ts":1616794345.5843055,"logger":"daemon.NodeConfigurator.loadModule","msg":"executing command","cmd":"/usr/sbin/chroot /host/ modprobe vfio-pci"}
        12. {"level":"Level(-4)","ts":1616794345.6090655,"logger":"daemon.NodeConfigurator.loadModule","msg":"commands output","output":""}
        13. {"level":"Level(-2)","ts":1616794345.6091156,"logger":"daemon.NodeConfigurator","msg":"device's driver_override path","path":"/sys/bus/pci/devices/0000:af:00.0/driver_override"}
        14. {"level":"Level(-2)","ts":1616794345.6091807,"logger":"daemon.NodeConfigurator","msg":"driver bind path","path":"/sys/bus/pci/drivers/pci-pf-stub/bind"}
        15. {"level":"Level(-2)","ts":1616794345.7488534,"logger":"daemon.NodeConfigurator","msg":"device's driver_override path","path":"/sys/bus/pci/devices/0000:b0:00.0/driver_override"}
        16. {"level":"Level(-2)","ts":1616794345.748938,"logger":"daemon.NodeConfigurator","msg":"driver bind path","path":"/sys/bus/pci/drivers/vfio-pci/bind"}
        17. {"level":"Level(-2)","ts":1616794345.7492096,"logger":"daemon.NodeConfigurator","msg":"device's driver_override path","path":"/sys/bus/pci/devices/0000:b0:00.1/driver_override"}
        18. {"level":"Level(-2)","ts":1616794345.7492566,"logger":"daemon.NodeConfigurator","msg":"driver bind path","path":"/sys/bus/pci/drivers/vfio-pci/bind"}
        19. {"level":"Level(-4)","ts":1616794345.74968,"logger":"daemon.NodeConfigurator.applyConfig","msg":"executing command","cmd":"/sriov_workdir/pf_bb_config ACC100 -c /sriov_artifacts/0000:af:00.0.ini -p 0000:af:00.0"}
        20. {"level":"Level(-4)","ts":1616794346.5203931,"logger":"daemon.NodeConfigurator.applyConfig","msg":"commands output","output":"Queue Groups: 0 5GUL, 0 5GDL, 4 4GUL, 4 4GDL\nNumber of 5GUL engines 8\nConfiguration in VF mode\nPF ACC100 configuration complete\nACC100 PF [0000:af:00.0] configuration complete!\n\n"}
        21. {"level":"Level(-4)","ts":1616794346.520459,"logger":"daemon.NodeConfigurator.enableMasterBus","msg":"executing command","cmd":"/usr/sbin/chroot /host/ setpci -v -s 0000:af:00.0 COMMAND"}
        22. {"level":"Level(-4)","ts":1616794346.5458736,"logger":"daemon.NodeConfigurator.enableMasterBus","msg":"commands output","output":"0000:af:00.0 @04 = 0142\n"}
        23. {"level":"Level(-4)","ts":1616794346.5459251,"logger":"daemon.NodeConfigurator.enableMasterBus","msg":"executing command","cmd":"/usr/sbin/chroot /host/ setpci -v -s 0000:af:00.0 COMMAND=0146"}
        24. {"level":"Level(-4)","ts":1616794346.5795262,"logger":"daemon.NodeConfigurator.enableMasterBus","msg":"commands output","output":"0000:af:00.0 @04 0146\n"}
        25. {"level":"Level(-2)","ts":1616794346.5795407,"logger":"daemon.NodeConfigurator.enableMasterBus","msg":"MasterBus set","pci":"0000:af:00.0","output":"0000:af:00.0 @04 0146\n"}
        26. {"level":"Level(-4)","ts":1616794346.6867144,"logger":"daemon.drainhelper.Run()","msg":"worker function - end","performUncordon":true}
        27. {"level":"Level(-4)","ts":1616794346.6896322,"logger":"daemon.drainhelper.uncordon()","msg":"starting uncordon attempts"}
        28. {"level":"Level(-2)","ts":1616794346.69735,"logger":"daemon.drainhelper.uncordon()","msg":"node uncordoned"}
        29. {"level":"Level(-4)","ts":1616794346.6973662,"logger":"daemon.drainhelper.Run()","msg":"cancelling the context to finish the leadership"}
        30. {"level":"Level(-4)","ts":1616794346.7029872,"logger":"daemon.drainhelper.Run()","msg":"stopped leading"}
        31. {"level":"Level(-4)","ts":1616794346.7030034,"logger":"daemon.drainhelper","msg":"releasing the lock (bug mitigation)"}
        32. {"level":"Level(-4)","ts":1616794346.8040674,"logger":"daemon.updateInventory","msg":"obtained inventory","inv":{"sriovAccelerators":[{"vendorID":"8086","deviceID":"0b32","pciAddress":"0000:20:00.0","driver":"","maxVirtualFunctions":1,"virtualFunctions":[]},{"vendorID":"8086","deviceID":"0d5c","pciAddress":"0000:af:00.0","driver":"pci-pf-stub","maxVirtualFunctions":16,"virtualFunctions":[{"pciAddress":"0000:b0:00.0","driver":"vfio-pci","deviceID":"0d5d"},{"pciAddress":"0000:b0:00.1","driver":"vfio-pci","deviceID":"0d5d"}]}]}}
        33. {"level":"Level(-4)","ts":1616794346.9058325,"logger":"daemon","msg":"Update ignored, generation unchanged"}
        34. {"level":"Level(-2)","ts":1616794346.9065044,"logger":"daemon.Reconcile","msg":"Reconciled","namespace":"vran-acceleration-operators","name":"pg-itengdvs02r.altera.com"}

    3. Check the FEC configuration of the card:

      1. $ oc get sriovfecnodeconfig node1 -o yaml

      Example output

      1The value 0d5c is the deviceID physical function of the FEC device.
      2The value is the deviceID virtual function of the FEC device.

    OpenNESS is an edge computing software toolkit that you can use to onboard and manage applications and network functions on any type of network.

    To verify all OpenNESS features are working together, including SR-IOV binding, the device plugin, Wireless Base Band Device (bbdev) configuration, and SR-IOV (FEC) VF functionality inside a non-root pod, you can build an image and run a simple validation application for the device.

    For more information, go to openess.org.

    Prerequisites

    • Node or nodes installed with the OpenNESS SR-IOV Operator for Wireless FEC Accelerators.

    • Real-Time kernel and huge pages configured with the Performance Addon Operator.

    Procedure

    1. Create a namespace for the test by completing the following actions:

      1. Define the test-bbdev namespace by creating a file named test-bbdev-namespace.yaml file as shown in the following example:

        1. apiVersion: v1
        2. kind: Namespace
        3. metadata:
        4.   name: test-bbdev
        5.   labels:
        6.     openshift.io/run-level: "1"

      2. Create the namespace by running the following command:

        1. $ oc create -f test-bbdev-namespace.yaml

    2. Create the following Pod specification, and then save the YAML in the pod-test.yaml file:

      1. apiVersion: v1
      2. kind: Pod
      3. metadata:
      4.   name: pod-bbdev-sample-app
      5.   namespace: test-bbdev (1)
      6. spec:
      7.   containers:
      8.   - securityContext:
      9.       privileged: false
      10.       capabilities:
      11.         add:
      12.         - IPC_LOCK
      13.         - SYS_NICE
      14.     name: bbdev-sample-app
      15.     image: bbdev-sample-app:1.0  (2)
      16.     command: [ "sudo", "/bin/bash", "-c", "--" ]
      17.     runAsUser: 0 (3)
      18.     resources:
      19.       requests:
      20.         hugepages-1Gi: 4Gi (4)
      21.         memory: 1Gi
      22.         cpu: "4" (5)
      23.         intel.com/intel_fec_acc100: '1' (6)
      24.       limits:
      25.         memory: 4Gi
      26.         cpu: "4"
      27.         hugepages-1Gi: 4Gi
      28.         intel.com/intel_fec_acc100: '1'
      1Specify the namespace you created in step 1.
      2This defines the test image containing the compiled DPDK.
      3Make the container execute internally as the root user.
      4Specify hugepage size hugepages-1Gi and the quantity of hugepages that will be allocated to the pod. Hugepages and isolated CPUs need to be configured using the Performance Addon Operator.
      5Specify the number of CPUs.
      6Testing of the ACC100 5G FEC configuration is supported by intel.com/intel_fec_acc100.

    3. Create the pod:

      1. $ oc apply -f pod-test.yaml

    4. Check that the pod is created:

      1. $ oc get pods -n test-bbdev

      Example output

      1. NAME                                            READY           STATUS          RESTARTS        AGE
      2. pod-bbdev-sample-app                            1/1             Running         0               80s

    5. Use a remote shell to log in to the pod-bbdev-sample-app:

      1. $ oc rsh pod-bbdev-sample-app

      Example output

      1. sh-4.4#

    6. Print the VF allocated to the pod:

      1. sh-4.4# printenv | grep INTEL_FEC

      Example output

      1. PCIDEVICE_INTEL_COM_INTEL_FEC_ACC100=0.0.0.0:1d.00.0 (1)

    7. Change to the test-bbdev directory.

      1. sh-4.4# cd test/test-bbdev/

    8. Check the CPUs that are assigned to the pod:

      1. sh-4.4# export CPU=$(cat /sys/fs/cgroup/cpuset/cpuset.cpus)
      2. sh-4.4# echo ${CPU}

      This prints out the CPUs that are assigned to the fec.pod.

      Example output

      1. 24,25,64,65

    9. Run the test-bbdev application to test the device:

      Example output

      ``` Executing: ../../build/app/dpdk-test-bbdev -l 24-25,64-65 0000:1d.00.0 — -n 64 -l 1 -c validation -v ./test_vectors/bbdev_null.data -b 32 EAL: Detected 80 lcore(s) EAL: Detected 2 NUMA nodes Option -w, —pci-whitelist is deprecated, use -a, —allow option instead EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode ‘VA’ EAL: Probing VFIO support… EAL: VFIO support initialized EAL: using IOMMU type 1 (Type 1) EAL: Probe PCI driver: intel_fpga_5ngr_fec_vf (8086:d90) device: 0000:1d.00.0 (socket 1) EAL: No legacy callbacks, legacy socket not created

    1. ===========================================================
    2. Starting Test Suite : BBdev Validation Tests
    3. Test vector file = ldpc_dec_v7813.data
    4. Device 0 queue 16 setup failed
    5. Allocated all queues (id=16) at prio0 on dev0
    6. Device 0 queue 32 setup failed
    7. Allocated all queues (id=32) at prio1 on dev0
    8. Device 0 queue 48 setup failed
    9. Allocated all queues (id=48) at prio2 on dev0
    10. Device 0 queue 64 setup failed
    11. Allocated all queues (id=64) at prio3 on dev0
    12. Device 0 queue 64 setup failed
    13. All queues on dev 0 allocated: 64
    14. + ------------------------------------------------------- +
    15. == test: validation
    16. dev:0000:b0:00.0, burst size: 1, num ops: 1, op type: RTE_BBDEV_OP_LDPC_DEC
    17. Operation latency:
    18.         avg: 23092 cycles, 10.0838 us
    19.         min: 23092 cycles, 10.0838 us
    20.         max: 23092 cycles, 10.0838 us
    21. TestCase [ 0] : validation_tc passed
    22.  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +
    23.  + Test Suite Summary : BBdev Validation Tests
    24.  + Tests Total :        1
    25.  + Tests Skipped :      0
    26.  + Tests Passed :       1 (1)
    27.  + Tests Failed :       0
    28.  + Tests Lasted :       177.67 ms
    29.  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +
    30. ```