From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3C562A0577; Mon, 6 Apr 2020 22:01:39 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A59F72B96; Mon, 6 Apr 2020 22:01:38 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 3EE242B83 for ; Mon, 6 Apr 2020 22:01:37 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 09927A057B; Mon, 6 Apr 2020 22:01:36 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Mon, 06 Apr 2020 20:01:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 19.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: christopher.swindle@metaswitch.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: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 444] DPDK fails to receive packets in Azure when using more than 3 transmit queues X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D444 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 u= sing 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 pack= ets (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=20=20 --vdev=3D"net_vdev_netvsc0,iface=3Deth1" --vdev=3D"net_vdev_netvsc1,iface= =3Deth2"=20=20 -- --forward-mode=3Drxonly --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 interfa= ces 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. --=20 You are receiving this mail because: You are the assignee for the bug.=