From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 444] DPDK fails to receive packets in Azure when using more than 3 transmit queues
Date: Mon, 06 Apr 2020 20:01:36 +0000 [thread overview]
Message-ID: <bug-444-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=444
Bug ID: 444
Summary: DPDK fails to receive packets in Azure when using more
than 3 transmit queues
Product: DPDK
Version: 19.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: christopher.swindle@metaswitch.com
Target Milestone: ---
I have setup two accelerated interfaces on Azure for use with DPDK and am using
the failsafe driver to bind to the interfaces, I find that if I set to use more
than 3 transmit queues then one of the interfaces will fail to receive packets
(even though there are no error shown).
Below is an example of the config that I use for a working case:
/usr/bin/testpmd -n 2 -w 0002:00:02.0 -w 0003:00:02.0
--vdev="net_vdev_netvsc0,iface=eth1" --vdev="net_vdev_netvsc1,iface=eth2"
-- --forward-mode=rxonly --nb-cores 1 --stats-period 1 --txq 3
If I change just the txq from 3 to 4, then rx packet counts do not go up for
both interfaces. If I increase this to 10 transmit queues then both interfaces
fail to receive packets.
I am currently running using the AKS image with the mxl4_ib module loaded
(although the same issue can also be seen when using ConnectX 5 devices in
Azure). As it seemed possible that it may have been a kernel issue, I also
updated my kernel to 5.0.0-1032-azure and the same behaviour is also seen.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-04-06 20:01 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-444-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 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.