DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1138] net/i40e all packets dropped after rte_eth_dev_flow_ctrl_set
Date: Thu, 01 Dec 2022 02:30:47 +0000	[thread overview]
Message-ID: <bug-1138-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1138
           Summary: net/i40e all packets dropped after
                    rte_eth_dev_flow_ctrl_set
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: hanshuang87@gmail.com
  Target Milestone: ---

My program call rte_eth_dev_flow_ctrl_set after rte_eth_dev_start. I found that
x710 dropped all packets(rx_dropped_packets in xstats).
I have used testpmd to confirm the problem:

diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
index da29858..eb11789 100755
--- a/app/test-pmd/testpmd.c
+++ b/app/test-pmd/testpmd.c
@@ -2928,6 +2928,16 @@ struct extmem_param {
                        continue;
                }

+               {
+                       struct rte_eth_fc_conf fc_conf = {
+                               .autoneg = 0,
+                               .mode = RTE_FC_NONE,
+                       };
+
+                       if (!rte_eth_dev_flow_ctrl_set(pi, &fc_conf))
+                               printf("set port %d flow ctrl\n", pi);
+               }
+
                if (port->port_status == RTE_PORT_HANDLING)
                        port->port_status = RTE_PORT_STARTED;
                else

If I stop and start the port again, packet will be received as good.

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

                 reply	other threads:[~2022-12-01  2:30 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-1138-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).