From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from userp2120.oracle.com (userp2120.oracle.com [156.151.31.85]) by dpdk.org (Postfix) with ESMTP id 701F85B1E; Thu, 3 Jan 2019 13:03:40 +0100 (CET) Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id x03Bt3ES108613; Thu, 3 Jan 2019 12:03:39 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type; s=corp-2018-07-02; bh=PdpA9N86eUwXa9jyhYu3Z3y0A8x+qGhpK6SaQpZYv/c=; b=Az3BoeIr7fET9R3Fvlbactki/HRPdQpYy24jHO66p/zBi5GLjwPkSYC8myauY6NUYqgr xIIJ1cB+zWtbR97AHhshAjPJeoyS3uk1N62qdrHpbMX1ahDn8kFbfPLY9A/Kdq4wfj2p V0BkAKllOr650KsN0klG1EiRzb5GLsDwqaKKH3b+/rQYUfGwfq9Tfa+TGtsf10gfxzMR wg0Ld49OqXojMt3OdSydLP7PPxrFJf3RaW6AwN2KDjSjIm/pMhpEoCfM68fn9io6Bx78 W3OrKanzbQ4vBM+4lAgGhflxXFoHnt6pC9EwvJqSW3SPblY0yxL7/GdNLkRC46sOzK3D Yg== Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2120.oracle.com with ESMTP id 2pp1jr6nk1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 03 Jan 2019 12:03:39 +0000 Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id x03C3crl015462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 3 Jan 2019 12:03:38 GMT Received: from abhmp0020.oracle.com (abhmp0020.oracle.com [141.146.116.26]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id x03C3bdD004782; Thu, 3 Jan 2019 12:03:37 GMT MIME-Version: 1.0 Message-ID: <20da4de9-e211-498c-bdfd-4dc4e827a66d@default> Date: Thu, 3 Jan 2019 12:03:33 +0000 (UTC) From: Vishnuvardhan Reddy Malispatel Sender: Vishnuvardhan Reddy Malispatel To: users@dpdk.org Cc: dev@dpdk.org References: In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 15.0.5093.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9124 signatures=668680 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=1 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=707 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901030107 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Only one Rx/Tx queue pair is assigned by DPDK PMD "net_bnxt" for BCM57414 VF X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jan 2019 12:03:40 -0000 Hi, =20 I have a guest virtual machine attached with BCM57414 Virtual Function . - When the BCM VF is owned by Linux driver "bnxt_en", I am seeing = two Rx/Tx queues are assigned by the driver. - When the same device is owned by DPDK PMD "net_bnxt" , I am seei= ng only one Rx/Tx queue is assigned and used by the PMD.=20 =20 Can someone help me in understanding the difference between the Linux drive= r behavior and DPDK PMD behavior in determining the number of queues for th= is specific VF ? =20 I am using the DPDK version "dpdk-17.11.4". =20 Thanks & Regards, Vishnu