[dpdk-dev] [PATCH v9 2/4] test/rcu_qsbr: add API and functional tests

David Marchand david.marchand at redhat.com
Fri May 3 16:31:19 CEST 2019


On Wed, May 1, 2019 at 5:55 AM Honnappa Nagarahalli <
honnappa.nagarahalli at arm.com> wrote:

> From: Dharmik Thakkar <dharmik.thakkar at arm.com>
>
> Add API positive/negative test cases, functional tests and
> performance tests.
>
> Signed-off-by: Malvika Gupta <malvika.gupta at arm.com>
> Signed-off-by: Dharmik Thakkar <dharmik.thakkar at arm.com>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli at arm.com>
> Reviewed-by: Gavin Hu <gavin.hu at arm.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev at intel.com>
>

Did not investigate, but this test always fails on my laptop.
Tried multiple times, I caught one instance when the test was still burning
cpu after 5 minutes and I killed it.

Usually, it fails like this:

[dmarchan at dmarchan dpdk]$ ./master/app/test -c 0x1f -n 4 --no-huge
EAL: Detected 8 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /run/user/114840/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: Started without hugepages support, physical addresses not available
EAL: PCI device 0000:00:1f.6 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 8086:15d7 net_e1000_em
APP: HPET is not enabled, using TSC as default timer
RTE>>rcu_qsbr_perf_autotest
Number of cores provided = 4
Perf test with all reader threads registered
--------------------------------------------

Perf Test: 3 Readers/1 Writer('wait' in qsbr_check == true)
Total RCU updates = 945401635
Cycles per 1000 updates: 25157
Total RCU checks = 20000000
Cycles per 1000 checks: 396375

Perf Test: 4 Readers
Total RCU updates = 400000000
Cycles per 1000 updates: 6241

Perf test: 4 Writers ('wait' in qsbr_check == false)
Total RCU checks = 80000000
Cycles per 1000 checks: 21061

Perf test: 1 writer, 4 readers, 1 QSBR variable, 1 QSBR Query, Blocking
QSBR Check
Reader did not complete #28 =  4097
Test Failed
RTE>>


-- 
David Marchand


More information about the dev mailing list