[dpdk-users] TX/RX adapter running on the same core problem

[Thomas Monjalon]

+Cc eventdev maintainers

26/09/2021 07:21, Jaeeun Ham:
> Hi,
> 
> I hope you are well.
> 
> During the traffic test, TX adapter showed starvation due to Rx adapter processing on the same dpdk-core 03 and dropped the 41412 packets after 154655 tx_retry.
> So, I expect I have to assign TX/RX adapter on each dpdk-core to prevent starvation and packet drop.
> 
> Are those tx_retry and tx_dropped packet due to RX adapter packet processing?
> Is it possible to separate TX/RX adapter into different dpdk-core?
> 
> ========[ TX adapter stats ]========
> tx_retry: 154655
> tx_packets: 438771
> tx_dropped: 41412
> 
> 
> < eventdev_dump.txt >
> ========[ Services ]========
> qdispatch_service_id    : 0
> txa_service_id          : 1
> rxa_service_id          : 2
> edk_service_id          : 3
> timer_service_id        : 4
> timer_adapter_service_id: 5
> 
> Service Cores Summary
> dpdk-core 01: PDCP Fastpath Plugin control function thread
> 
> dpdk-core   qu-dispat   txadapter   rxadapter         edk         tmr   tmr-adapt
>        03           0   770574949   770574948           0           0           0
>        05   816421027           0           0   816421571   816421571   816421571
>        07   896307282           0           0   896307828   896307828           0
>        09   899213296           0           0   899213687   899213687           0
>        11   889323680           0           0   889323871   889323871           0
>        13   897300534           0           0   897300686   897300686           0
>        15   891124716           0           0   891124811   891124811           0
>        17   896336177           0           0   896336212   896336211           0
>        19   895461845           0           0   895461846   895461846           0
> 
> ========[ Event dev port 0 ~ 10 xstats ]========
> - packet flow: f1u -> s1u one way
>   midhaul_ker -> midhaul_edk -> backhaul_edk -> backhaul_ker
>   port 09 Rx adapter -> port 07 -> port 06 -> port 08 -> port 09 Tx adapter
> 
> port 00: dpdk-core 05, worker_core // queue-dispatcher, edk, timer
> port 01: dpdk-core 07, worker_core // queue-dispatcher, edk, timer
> port 02: dpdk-core 09, worker_core // queue-dispatcher, edk, timer
> port 03: dpdk-core 11, worker_core // queue-dispatcher, edk, timer
> port 04: dpdk-core 13, worker_core // queue-dispatcher, edk, timer
> port 05: dpdk-core 15, worker_core // queue-dispatcher, edk, timer
> port 06: dpdk-core 17, worker_core // queue-dispatcher, edk, timer
> port 07: dpdk-core 19, worker_core // queue-dispatcher, edk, timer
> port 08: TX adapter, dpdk-core 03  // packet transmission
> port 09: RX adapter, dpdk-core 03  // packet receiving
> port 10: Event timer adapter       // tmr-adapter
> 
> BR/Jaeeun
> -------------- next part --------------
> An embedded and charset-unspecified text was scrubbed...
> Name: eventdev_dump.txt
> URL: <http://mails.dpdk.org/archives/users/attachments/20210926/bbf13055/attachment.txt>
>