From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id 6B49B46F59;
Fri, 19 Sep 2025 22:15:03 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 309344042F;
Fri, 19 Sep 2025 22:15:03 +0200 (CEST)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
by mails.dpdk.org (Postfix) with ESMTP id CCF74402B7
for ; Fri, 19 Sep 2025 22:15:01 +0200 (CEST)
Received: by inbox.dpdk.org (Postfix, from userid 33)
id C5DBA46F5A; Fri, 19 Sep 2025 22:15:01 +0200 (CEST)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1789] vmxnet3_dev_start fails in
vmxnet3_v4_rss_configure() for single queue in ESX8.0 causing application to
exit
Date: Fri, 19 Sep 2025 20:15:01 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: ethdev
X-Bugzilla-Version: 19.11
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amiyaranjan.mohakud@gmail.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
op_sys bug_status bug_severity priority component assigned_to reporter
target_milestone
Message-ID:
Content-Type: multipart/alternative; boundary=17583129010.14cDfbA7.1511821
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dev-bounces@dpdk.org
--17583129010.14cDfbA7.1511821
Date: Fri, 19 Sep 2025 22:15:01 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
https://bugs.dpdk.org/show_bug.cgi?id=3D1789
Bug ID: 1789
Summary: vmxnet3_dev_start fails in vmxnet3_v4_rss_configure()
for single queue in ESX8.0 causing application to exit
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: amiyaranjan.mohakud@gmail.com
Target Milestone: ---
DPDK Version: 19.11
ESX version: ESX8.0
We faced an exact similar issue as mentioned in
https://mails.dpdk.org/archives/users/2025-April/008236.html.=20
Context Details:
-----------------
In ESXi 8.0 setup with dpdk-19.11, when the HW compatibility version is ESX=
8.0
and with single queue pair configuration, the RSS gets enabled. As a result,
vmxnet3_v4_rss_configure() gets called and fails while writing/reading from
BAR1 hw register. It looks to be some compatibility issue with dpdk-19.11 a=
nd
ESX8.0.
if (VMXNET3_VERSION_GE_4(hw) &&=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
dev->data->dev_conf.rxmode.mq_mode =3D=3D ETH_MQ_RX_RSS) {=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20
/* Check for additional RSS */=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
ret =3D vmxnet3_v4_rss_configure(dev);=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
if (ret !=3D VMXNET3_SUCCESS) {=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
PMD_INIT_LOG(ERR, "Failed to configure v4 RSS");=20=
=20=20=20=20=20=20=20
return ret;=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20
}=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
}=20=20
As a result, it causes the application to exit.
Proposed fix:
I have a plausible fix for this. The fix is to disable RSS for such a case (
the fix should go only in 19.11). During dev_configure(), we can set the
mq_mode to ETH_MQ_RX_NONE if the num_rx_queues is 1. This would avoid call=
ing
of vmxnet3_v4_rss_configure().
/* Disabling RSS for single queue pair */=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
if (dev->data->nb_rx_queues =3D=3D 1) {=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20
dev->data->dev_conf.rxmode.mq_mode =3D ETH_MQ_RX_NONE;=20=
=20=20=20=20=20=20=20=20=20=20=20
PMD_INIT_LOG(ERR, "WARN: Disabling RSS for single Rx queue"=
);=20=20=20
}
Pls verify and let me know if it can be upstreamed. Once confirmed/approved=
, If
required, I can generate a main stream patch for it.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--17583129010.14cDfbA7.1511821
Date: Fri, 19 Sep 2025 22:15:01 +0200
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
vmxnet3_dev_start fails in vmxnet3_v4_rss_configure() for sin=
gle queue in ESX8.0 causing application to exit
Product
DPDK
Version
19.11
Hardware
All
OS
All
Status
UNCONFIRMED
Severity
normal
Priority
Normal
Component
ethdev
Assignee
dev@dpdk.org
Reporter
amiyaranjan.mohakud@gmail.com
Target Milestone
---
DPDK Version: 19.11
ESX version: ESX8.0
We faced an exact similar issue as mentioned in
ht=
tps://mails.dpdk.org/archives/users/2025-April/008236.html.=20
Context Details:
-----------------
In ESXi 8.0 setup with dpdk-19.11, when the HW compatibility version is ESX=
8.0
and with single queue pair configuration, the RSS gets enabled. As a result,
vmxnet3_v4_rss_configure() gets called and fails while writing/reading from
BAR1 hw register. It looks to be some compatibility issue with dpdk-19.11 a=
nd
ESX8.0.
if (VMXNET3_VERSION_GE_4(hw) &&=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20
dev->data->dev_conf.rxmode.mq_mode =3D=3D ETH_MQ_RX_RSS) =
{=20=20=20=20=20=20=20=20=20=20=20=20=20=20
/* Check for additional RSS */=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
ret =3D vmxnet3_v4_rss_configure(dev);=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
if (ret !=3D VMXNET3_SUCCESS) {=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
PMD_INIT_LOG(ERR, "Failed to configure v4 RSS&=
quot;);=20=20=20=20=20=20=20=20
return ret;=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20
}=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
}=20=20
As a result, it causes the application to exit.
Proposed fix:
I have a plausible fix for this. The fix is to disable RSS for such a case (
the fix should go only in 19.11). During dev_configure(), we can set the
mq_mode to ETH_MQ_RX_NONE if the num_rx_queues is 1. This would avoid call=
ing
of vmxnet3_v4_rss_configure().
/* Disabling RSS for single queue pair */=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
if (dev->data->nb_rx_queues =3D=3D 1) {=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20
dev->data->dev_conf.rxmode.mq_mode =3D ETH_MQ_RX_NONE=
;=20=20=20=20=20=20=20=20=20=20=20=20
PMD_INIT_LOG(ERR, "WARN: Disabling RSS for single Rx q=
ueue");=20=20=20
}
Pls verify and let me know if it can be upstreamed. Once confirmed/approved=
, If
required, I can generate a main stream patch for it.