All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 2147] [Bug] net/e1000: queue-count regression on VMware Workstation 82545EM
Date: Wed, 18 Nov 2026 04:28:33 +0000	[thread overview]
Message-ID: <bug-2147-3@https.bugs.dpdk.org/> (raw)

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

            Bug ID: 2147
           Summary: [Bug] net/e1000: queue-count regression on VMware
                    Workstation 82545EM
           Product: DPDK
           Version: 26.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: liuwf@ysxt.com.cn
  Target Milestone: ---

Hi,

We observed a networking regression after upgrading an integrated DPDK
application from 22.11.1 to 22.11.11 on a virtual Intel 82545EM copper NIC
(net_e1000_em) in VMware Workstation. Limiting the application to one RX/TX
queue on 22.11.11 restores both ping and SSH connectivity on the affected VM.

Observed on 22.11.11:
- Device/application initialization reports no error.
- RX counters increase, but ping and SSH to the management IP fail.
- The application now configures two RX/TX queues; startup output confirms
  a binding for queue 1. It selects the queue count using the advertised
  RX/TX maximums and the available worker threads.

The relevant upstream change identified by source comparison is:
  c1a42d646472 ("net/e1000: fix queue number initialization")

That change unconditionally raises max_rx_queues and max_tx_queues from
1 to 2. However, the adjacent comment still describes limitations that
led to the single-queue implementation: extended RX descriptors are
required for multiple RX queues, 82540/82545 do not support those
extended descriptors, and the TX queues share a TX context.

The same unconditional values and comment remain in main at
c6d273ce156cc48ef90e64e93a2bba80c9d36345 (VERSION 26.11.0-rc3), and in
v26.07 and v25.11.4. These newer versions were inspected in source only;
we have not reproduced the runtime failure on them.

We applied an application-side workaround limiting EM ports to one RX
queue and one TX queue. Local tests using the production queue-selection and
TX-routing
functions show the original upgraded configuration selecting queue 1,
and the workaround keeping traffic on queue 0. Compilation with our
GCC 4.8.5 toolchain succeeds.

On-device results on VMware Workstation:
- 22.11.1 with the original single-queue behavior: networking worked.
- 22.11.11 with two queues, including an observed queue 1 binding:
  ping and SSH failed despite RX counters increasing.
- 22.11.11 with the single-queue workaround deployed:
  both ping and SSH connectivity recovered.

A stock testpmd reproduction and a commit-by-commit runtime bisection are
not yet available; the runtime results above are from our integrated
application on the affected VMware Workstation VM.

Could you confirm which devices were intended to support two queues in
c1a42d646472, and whether legacy/virtual 82545EM devices should still be
limited to one RX/TX queue? Should these capabilities be reported per
MAC/device type instead of unconditionally for the entire EM driver?

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

                 reply	other threads:[~2026-11-18  4:28 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-2147-3@https.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.