From: Stephen Hemminger <stephen@networkplumber.org>
To: Yongseok Koh <yskoh@mellanox.com>, Shahaf Shuler <shahafs@mellanox.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] Please revert mlx IOVA VA mode patch
Date: Fri, 7 Jun 2019 11:33:24 -0700 [thread overview]
Message-ID: <20190607113324.25248eba@hermes.lan> (raw)
The Netvsc PMD got broken on DPDK 19.08 by a bad patch in Mellanox driver.
On a simple setup with SRIOV enabled and using netvsc PMD with the testpmd.
It worked in 19.05 and does not work with current master.
The probe code gets stuck because netvsc PMD sends a request to host
and never sees a response.
# ./build/app/testpmd --log-level='pmd.net.netvsc.*:debug' -l 0-3 -n 4 -- --rxq=4 --txq=4 -i
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
EAL: PCI device 935f:00:02.0 on NUMA socket 0
EAL: probe driver: 15b3:1014 net_mlx5
net_mlx5: can not get IB device "mlx5_0" ports number
eth_hn_probe(): >>
eth_hn_dev_init(): >>
hn_nvs_init(): NVS version 0x60001, NDIS version 6.30
hn_nvs_conn_rxbuf(): connect rxbuff va=0x2200402000 gpad=0xe1e2d
hn_nvs_conn_rxbuf(): receive buffer size 1728 count 18811
hn_nvs_conn_chim(): connect send buf va=0x2202302000 gpad=0xe1e2e
hn_nvs_conn_chim(): send buffer 16777216 section size:6144, count:2730
(hung)
The problem does not occur without SRIOV (or if MLX driver is not
compiled in).
Doing bisect the problem is caused by:
commit 69c06d0e357ed0064b498d510d169603cf7308cd
Author: Yongseok Koh <yskoh@mellanox.com>
Date: Thu May 2 02:07:54 2019 -0700
net/mlx: support IOVA VA mode
Set RTE_PCI_DRV_IOVA_AS_VA to driver's drv_flags as device's IOMMU takes
virtual address.
Cc: stable@dpdk.org
Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
Acked-by: Shahaf Shuler <shahafs@mellanox.com>
Please either revert or fix this patch ASAP.
next reply other threads:[~2019-06-07 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 18:33 Stephen Hemminger [this message]
2019-06-07 21:59 ` Yongseok Koh
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=20190607113324.25248eba@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=yskoh@mellanox.com \
/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).