From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 609] Nic stops receiving traffic and rx missed counter starts increasing on Intel igb I350 Nics
Date: Thu, 07 Jan 2021 18:59:41 +0000 [thread overview]
Message-ID: <bug-609-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=609
Bug ID: 609
Summary: Nic stops receiving traffic and rx missed counter
starts increasing on Intel igb I350 Nics
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: arjit@haltdos.com
Target Milestone: ---
Created attachment 140
--> https://bugs.dpdk.org/attachment.cgi?id=140&action=edit
Nic Config
I have a dpdk based application that is reading packets from the nic and
sending them out to the other nic. The issue is after some time nic stops
reading any traffic and rx_missed counter starts increasing. I have monitored
the packet pool configured for the nic and verified that mempool is not getting
full.
I have attached the nic config screenshot. I have configured 2 queues for the
nic and both the queues are handled by separate cores.This issue occurs
intermittently even on low traffic and link status still shows the link as
active.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-01-07 18:59 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-609-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).