DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1573] NIC latency issue on the AsyncSniffer callback function
Date: Wed, 30 Oct 2024 16:55:41 +0000	[thread overview]
Message-ID: <bug-1573-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1573
           Summary: NIC latency issue on the AsyncSniffer callback
                    function
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: DTS
          Assignee: dev@dpdk.org
          Reporter: npratte@iol.unh.edu
                CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
  Target Milestone: ---

There exists a bug on i40e NICs where the AsyncSniffer does not capture sent
packets forwarded by the callback function. As if now, it's unclear why this
would be the case, but there is a temporary fix that adds a simple one second
delay to the callback function and packet sniffing duration before sending out
any packets. This temporary fix allows test cases to perform as expected on
i40e devices while maintaining the output of other vendors as well. It is in
the best interest of the framework to find a better solution to this problem,
but for the time being, this temporary fix will suffice.

This ticket will remain open until such a time arises where a better solution
is proposed once further research is conducted.

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

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

                 reply	other threads:[~2024-10-30 16:55 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-1573-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).