From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 8FB19A0096 for ; Thu, 6 Jun 2019 01:10:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BA6A31B9E9; Thu, 6 Jun 2019 01:10:35 +0200 (CEST) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by dpdk.org (Postfix) with ESMTP id 7CD021B9E7 for ; Thu, 6 Jun 2019 01:10:33 +0200 (CEST) Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x55N25oI085925 for ; Wed, 5 Jun 2019 19:10:32 -0400 Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0a-001b2d01.pphosted.com with ESMTP id 2sxmmbpd1b-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 05 Jun 2019 19:10:32 -0400 Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 6 Jun 2019 00:10:31 +0100 Received: from b03cxnp07028.gho.boulder.ibm.com (9.17.130.15) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Thu, 6 Jun 2019 00:10:30 +0100 Received: from b03ledav001.gho.boulder.ibm.com (b03ledav001.gho.boulder.ibm.com [9.17.130.232]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x55NAT3N16974160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 5 Jun 2019 23:10:29 GMT Received: from b03ledav001.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A1A506E052; Wed, 5 Jun 2019 23:10:29 +0000 (GMT) Received: from b03ledav001.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 033B66E064; Wed, 5 Jun 2019 23:10:28 +0000 (GMT) Received: from davids-mbp.usor.ibm.com (unknown [9.70.84.137]) by b03ledav001.gho.boulder.ibm.com (Postfix) with ESMTP; Wed, 5 Jun 2019 23:10:28 +0000 (GMT) To: "Wiles, Keith" Cc: "dev@dpdk.org" References: <671a1e2e-cf45-e86f-01ef-3c05530ab067@linux.vnet.ibm.com> From: David Christensen Date: Wed, 5 Jun 2019 16:10:28 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 19060523-8235-0000-0000-00000EA430DD X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00011221; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000286; SDB=6.01213790; UDB=6.00637983; IPR=6.00994863; MB=3.00027200; MTD=3.00000008; XFM=3.00000015; UTC=2019-06-05 23:10:31 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19060523-8236-0000-0000-000045E1D82C Message-Id: <0e2af1b7-2b5f-52ed-a2d5-62f1465a6733@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-05_15:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906050146 Subject: Re: [dpdk-dev] Pktgen Only Enables One RX Queue with Mellanox ConnectX-5 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" >> Traffic is only received on RX queue 0. Anyone run into this? The link partner shows traffic received and transmitted on all configured queues (16 in this case) so I don't think the link partner is dropping traffic in such a way that the remaining traffic flows to a single RX queue on the SUT. > > This normally means the RSS is not distributing the RX traffic to the others, which means the RX traffic is not varied enough to make RSS distribute the traffic. That would be my best guess I have not used the Mellanox cards. Remember that the traffic is being generated by pktgen. Is there something I can improve with the "range" commands I used to start the test? When I review the extended statistics from testpmd's "show port xstats all" command I see that traffic is being distributed correctly when received by the SUT (i.e. each per RX queue statistic is incrementing and is about the same value). And the SUT uses the same MLX5 adapter that the pktgen host does. Similarly, the per TX queue statistic is incrementing as well, suggesting that the traffic is being looped back to the pktgen host. If there's a problem with RSS it would appear to be on the pktgen host side. Is that expected? I haven't looked into how RSS is enabled with DPDK but it looks like pktgen operates differently with respect to RSS on different versions of DPDK. Does the following code snippet mean that RSS isn't enabled by pktgen on my build of DPDK v18.11? app/pktgen-port-cfg.c: 41 static struct rte_eth_conf default_port_conf = {$ 42 #if RTE_VERSION <= RTE_VERSION_NUM(18, 5, 0, 0)$ 43 | .rxmode = {$ 44 | | .mq_mode = ETH_MQ_RX_RSS,$ 45 | | .max_rx_pkt_len = ETHER_MAX_LEN,$ 46 | | .split_hdr_size = 0,$ 47 | | .ignore_offload_bitfield = 1,$ 48 | | .offloads = (DEV_RX_OFFLOAD_CRC_STRIP |$ 49 | | | DEV_RX_OFFLOAD_CHECKSUM),$ 50 | },$ 51 | .rx_adv_conf = {$ 52 | | .rss_conf = {$ 53 | | | .rss_key = NULL,$ 54 | | | .rss_hf = ETH_RSS_IP,$ 55 | | },$ 56 | },$ 57 | .txmode = {$ 58 | | .mq_mode = ETH_MQ_TX_NONE,$ 59 | },$ 60 #else$ 61 | .rxmode = {$ 62 | | .split_hdr_size = 0,$ Dave