numam-dpdk/app/test-eventdev/Makefile

33 lines
601 B
Makefile
Raw Normal View History

# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2017 Cavium, Inc
#
include $(RTE_SDK)/mk/rte.vars.mk
APP = dpdk-test-eventdev
CFLAGS += -O3
CFLAGS += $(WERROR_FLAGS)
#
# all source are stored in SRCS-y
#
SRCS-y := evt_main.c
SRCS-y += evt_options.c
SRCS-y += evt_test.c
SRCS-y += parser.c
SRCS-y += test_order_common.c
SRCS-y += test_order_queue.c
SRCS-y += test_order_atq.c
SRCS-y += test_perf_common.c
app/testeventdev: add perf queue test This is a performance test case that aims at testing the following: 1. Measure the number of events can be processed in a second. 2. Measure the latency to forward an event. The perf queue test configures the eventdev with Q queues and P ports, where Q is nb_producers * nb_stages and P is nb_workers + nb_producers. The user can choose the number of workers, the number of producers and number of stages through the --wlcores , --plcores and the --stlist application command line arguments respectively. The producer(s) injects the events to eventdev based the first stage sched type list requested by the user through --stlist the command line argument. Based on the number of stages to process(selected through --stlist), the application forwards the event to next upstream queue and terminates when it reaches the last stage in the pipeline. On event termination, application increments the number events processed and print periodically in one second to get the number of events processed in one second. When --fwd_latency command line option selected, the application inserts the timestamp in the event on the first stage and then on termination, it updates the number of cycles to forward a packet. The application uses this value to compute the average latency to a forward packet. Example command to run perf queue test: sudo build/app/dpdk-test-eventdev --vdev=event_sw0 -- --test=perf_queue\ --slcore=1 --plcores=2 --wlcore=3 --stlist=p --nb_pkts=1000000000 Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-07-04 04:53:19 +00:00
SRCS-y += test_perf_queue.c
SRCS-y += test_perf_atq.c
SRCS-y += test_pipeline_common.c
app/eventdev: add pipeline queue test This is a pipeline queue test case that aims at testing the following: 1. Measure the end-to-end performance of an event dev with a ethernet dev. 2. Maintain packet ordering from Rx to Tx. The pipeline queue test configures the eventdev with Q queues and P ports, where Q is (nb_ethdev * nb_stages) + nb_ethdev and P is nb_workers. The user can choose the number of workers and number of stages through the --wlcores and the --stlist application command line arguments respectively. The probed ethernet devices act as producer(s) for this application. The ethdevs are configured as event Rx adapters that enables them to injects events to eventdev based the first stage schedule type list requested by the user through --stlist the command line argument. Based on the number of stages to process(selected through --stlist), the application forwards the event to next upstream queue and when it reaches last stage in the pipeline if the event type is ATOMIC it is enqueued onto ethdev Tx queue else to maintain ordering the event type is set to ATOMIC and enqueued onto the last stage queue. On packet Tx, application increments the number events processed and print periodically in one second to get the number of events processed in one second. Note: The --prod_type_ethdev is mandatory for running the application. Example command to run pipeline queue test: sudo build/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=event_sw0 -- \ --test=pipeline_queue --wlcore=1 --prod_type_ethdev --stlist=ao Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2018-01-16 17:46:01 +00:00
SRCS-y += test_pipeline_queue.c
SRCS-y += test_pipeline_atq.c
include $(RTE_SDK)/mk/rte.app.mk