From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1346] net/i40e does not report interrupt for the second packet
Date: Tue, 09 Jan 2024 19:24:03 +0000 [thread overview]
Message-ID: <bug-1346-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1346
Bug ID: 1346
Summary: net/i40e does not report interrupt for the second
packet
Product: DPDK
Version: 23.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: andrew.rybchenko@oktetlabs.ru
Target Milestone: ---
net/i40e does not report interrupt for the second packet
If I understand Rx interrupts functionality correctly, Rx interrupts should be
generated until disabled. However, it does not happen in the case of i40e with
X710 NIC.
The problem is found by open-source test suite which has been run at UNH IOL
[1].
Scenario is simple:
- enable Rx interrupts
- send packet from peer
- check interrupt, receive packet
- send one more packet
- check interrupt - failure, no interupt
[1]
https://ts-factory.io/bublik/v2/log/362398?mode=treeAndlog&focusId=363533&experimental=true&lineNumber=1_69
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3201 bytes --]
reply other threads:[~2024-01-09 19:24 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-1346-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).