From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 834] eventdev/eth_rx: callback not invoked in vector timeout case
Date: Mon, 25 Oct 2021 07:08:06 +0000 [thread overview]
Message-ID: <bug-834-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=834
Bug ID: 834
Summary: eventdev/eth_rx: callback not invoked in vector
timeout case
Product: DPDK
Version: 21.08
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: eventdev
Assignee: dev@dpdk.org
Reporter: s.v.naga.harish.k@intel.com
Target Milestone: ---
Hi all,
In Rx_adapter,
the pending events vectors are checked in the service function for timeout
case. Incase of timeout, the event is made ready by removing the event vector
from the pending vector list and updating event buffer count in
rxa_vector_expire function.
The rx_adapter registered callback function is not invoked inside
rxa_vector_expire function for these timeout vectors.
The expected behavior is that, the callback function need to be invoked for all
successful enqueued packets to event buffer.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-10-25 7:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-834-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).