From: Hari Haran <info2hariharan@gmail.com>
To: users@dpdk.org
Subject: Inflight value shown invalid in Event Dev Queue
Date: Wed, 19 Jul 2023 18:09:15 +0530 [thread overview]
Message-ID: <CAPbxCtoxG=vV1q7RnNZT5-1MzaocCG12fAO4gmkFVCwg0foTrA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
Hi All,
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 .
*Port 0 Stats:*
Below case, port 0 dequeued 4096 packets and still inflight showed the same
value.
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
[-- Attachment #2: Type: text/html, Size: 2044 bytes --]
next reply other threads:[~2023-07-19 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 12:39 Hari Haran [this message]
2023-07-19 12:58 ` Van Haaren, Harry
2023-07-19 15:30 ` Hari Haran
2023-07-19 16:17 ` Van Haaren, Harry
2023-08-29 14:50 ` Hari Haran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPbxCtoxG=vV1q7RnNZT5-1MzaocCG12fAO4gmkFVCwg0foTrA@mail.gmail.com' \
--to=info2hariharan@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).