DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1345] net/i40e packet loss after Rx interrupt disable
Date: Tue, 09 Jan 2024 18:14:08 +0000	[thread overview]
Message-ID: <bug-1345-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1345

            Bug ID: 1345
           Summary: net/i40e packet loss after Rx interrupt disable
           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 packet loss after Rx interrupt disable

Open-source test suite which has been run at UNH IOL has a number of test
scenarios which check Rx interrupts support.
There is a common pattern of failures in 4 cases. If Rx interrupt is disabled,
the next packet to be received is lost [1], [2], [3] and [4].

[1]
https://ts-factory.io/bublik/v2/log/362398?mode=treeAndlog&focusId=363531&experimental=true&lineNumber=1_75
[2]
https://ts-factory.io/bublik/v2/log/362398?mode=treeAndlog&focusId=363534&experimental=true&lineNumber=1_75
[3]
https://ts-factory.io/bublik/v2/log/362398?mode=treeAndlog&focusId=363535&experimental=true&lineNumber=1_58
[4]
https://ts-factory.io/bublik/v2/log/362398?mode=treeAndlog&focusId=363536&experimental=true&lineNumber=1_79

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3783 bytes --]

                 reply	other threads:[~2024-01-09 18:14 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-1345-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).