Hi Harry Haaren (Yes :) )

I have given more details below, please check this.

Device Configuration:
Event Dev Queue : 1
Number of ports : 3

Queue 0 depth - 32k
Port 0, 1 amd 2 : Enqueue depth 4096, Dequeue depth 128

Cores:
Rx core - 1
Workers cores - 2

Port 2:
Used in Rx core - Used to post packets from Rx core to worker cores using event dev queue .
So port 2 used to post packets only.
API used: rte_event_enqueue_burst()

Port 0 and 1 linked with Event Dev Q 0 to dequeue the packets. These ports used to dequeue the packets only.
Port 0 used in Worker core 1 - Only to receive the packets from Rx core using event dev queue
Port 1 used in worker core 2 - Only to receive the packets from Rx core using event dev queue
API used: rte_event_dequeue_burst()

Expected behaviour:

Port 2 enqueue packets to event dev Q in Rx core
Port 0 and 1 dequeue packets from event dev Q in two workers

Event dev scheduler of queue 0, will schedule received packets in port 2 to port 0 and 1.

Problem Description:

Port 0 - only received 4096 packets through event dev Q, after that no packets available for this.
API used: rte_event_dequeue_burst()

Port 2 - Successfully enqueued 32k packets through event dev Q, after that enqueue failure observed.
API used: rte_event_enqueue_burst()

Looks like, event dev queue stalled at this point.

Also why port 0 stats show inflight as 4096?

Port 0 Stats:
rx   0 drop 0 tx   4096   inflight 4096

All Stats:
Dev=0 Port=1EventDev todo-fix-name: ports 3, qids 1
rx   32768
drop 0
tx   4096
sched calls: 628945658
sched cq/qid call: 628964843
sched no IQ enq: 628926401
sched no CQ enq: 628942982
inflight 32768, credits: 0

Port 0
rx   0 drop 0 tx   4096   inflight 4096
Max New: 32768 Avg cycles PP: 0    Credits: 0
Receive burst distribution:
      0:100% 1-4:0.00% 5-8:0.00% 9-12:0.00%
rx ring used:    0 free: 4096
cq ring used:    0 free: 128
Port 1
rx   0 drop 0 tx   0 inflight 0
Max New: 32768 Avg cycles PP: 0    Credits: 0
Receive burst distribution:
      0:100%
rx ring used:    0 free: 4096
cq ring used:    0 free: 128
Port 2
rx   32768 drop 0 tx   0 inflight 0
Max New: 32768 Avg cycles PP: 0    Credits: 0
Receive burst distribution:
      0:-nan%
rx ring used:    0 free: 4096
cq ring used:    0 free: 128

Queue 0 (Atomic)
rx   32768 drop 0 tx   4096
Per Port Stats:
    Port 0: Pkts: 4096    Flows: 1
    Port 1: Pkts: 0   Flows: 0
    Port 2: Pkts: 0   Flows: 0
    Port 3: Pkts: 0   Flows: 0
iq 0: Used 28672

Regards,

Hariharan

On Wed, Jul 19, 2023 at 6:30 PM Van Haaren, Harry <harry.van.haaren@intel.com> wrote:

> From: Hari Haran <info2hariharan@gmail.com>
> Sent: Wednesday, July 19, 2023 1:39 PM
> To: users@dpdk.org
> Subject: Inflight value shown invalid in Event Dev Queue
>
> Hi All,

Hi Hari Haran,

> Once packets dequeued from port 0, still inflight stats shown same as dequeued count.
> After that, enqueue failure happens for port 2 from another core due to it reaches Max Enqueue depth .

This describes what happens -> it would be helpful to know what you are expecting to happen.
Would you describe what each of port 0,1,2 are actually used for, and how events are expected
to flow from RX to a Port through a Queue, to another Port, until TX?

Describing the expectation and then comparing that to your "problem description" in this email often
leads to the root cause & solution.

Keep in mind that the event/sw implementation has capacity limitations. It seems to be too high in your configuration
(inflight = 32768 is a indicator of an issue, as SW_INFLIGHT_EVENTS_TOTAL is 4096 in sw_evdev.h).

> Port 0 Stats:
>
> Below case, port 0 dequeued 4096 packets and still inflight showed the same value.

How are the events being re-enqueued?

> Port 0
> rx 0 drop 0 tx 4096 inflight 4096
>
> Full Stats:
>
> Dev=0 Port=1EventDev todo-fix-name: ports 3, qids 1
> rx 32768
> drop 0
> tx 4096
> sched calls: 628945658
> sched cq/qid call: 628964843
> sched no IQ enq: 628926401
> sched no CQ enq: 628942982
> inflight 32768, credits: 0
>
> Port 0
> rx 0 drop 0 tx 4096 inflight 4096
> Max New: 32768 Avg cycles PP: 0 Credits: 0
> Receive burst distribution:
> 0:100% 1-4:0.00% 5-8:0.00% 9-12:0.00%
> rx ring used: 0 free: 4096
> cq ring used: 0 free: 128
> Port 1
> rx 0 drop 0 tx 0 inflight 0
> Max New: 32768 Avg cycles PP: 0 Credits: 0
> Receive burst distribution:
> 0:100%
> rx ring used: 0 free: 4096
> cq ring used: 0 free: 128
> Port 2
> rx 32768 drop 0 tx 0 inflight 0
> Max New: 32768 Avg cycles PP: 0 Credits: 0
> Receive burst distribution:
> 0:-nan%
> rx ring used: 0 free: 4096
> cq ring used: 0 free: 128
>
> Queue 0 (Atomic)
> rx 32768 drop 0 tx 4096
> Per Port Stats:
> Port 0: Pkts: 4096 Flows: 1
> Port 1: Pkts: 0 Flows: 0
> Port 2: Pkts: 0 Flows: 0
> Port 3: Pkts: 0 Flows: 0
> iq 0: Used 28672
> This issue will be resolved once system level restart is done.
> Kindly give insight on this issue, if you found any clues.
> TIA.
>
> Regards
> Hariharan

Regards, -Harry van Haaren (PS: our names are surprisingly similar! : )