From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by dpdk.org (Postfix) with ESMTP id 27F70271 for ; Tue, 8 Jan 2019 19:38:43 +0100 (CET) Received: from mail.fortinet.com ([192.168.221.212]) by smtp.fortinet.com with ESMTP id x08Ich22024181-x08Ich24024181 (version=TLSv1.0 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 8 Jan 2019 10:38:43 -0800 Received: from FGT-EXCH-MBX133.fortinet-us.com (192.168.221.133) by FGT-EXCH-CAS212.fortinet-us.com (192.168.221.212) with Microsoft SMTP Server (TLS) id 14.3.389.1; Tue, 8 Jan 2019 10:38:43 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com (192.168.221.132) by FGT-EXCH-MBX133.fortinet-us.com (192.168.221.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Tue, 8 Jan 2019 10:38:42 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com ([fe80::78b9:5f97:8cec:b419]) by FGT-EXCH-MBX132.fortinet-us.com ([fe80::78b9:5f97:8cec:b419%11]) with mapi id 15.01.1531.003; Tue, 8 Jan 2019 10:38:42 -0800 From: Liwu Liu To: Stephen Hemminger CC: "users@dpdk.org" Thread-Topic: [dpdk-users] Cannot run DPDK applications using Mellanox NIC under Hyper-V Thread-Index: AdSkaIlXmtS1/HLnTKOuGVPhM0hYtgAZRFKAABClZND//3+XgIAAhQ0g//+HTQD/+qnGIA== Date: Tue, 8 Jan 2019 18:38:41 +0000 Message-ID: References: <20190104160647.7f17e932@hermes.lan> <596318879eb14b32971e4c182489f537@fortinet.com> <20190104162349.264da710@hermes.lan> <02a2fbe93b93458190386e8650c3fb2c@fortinet.com> <20190104170802.4ed27cce@hermes.lan> In-Reply-To: <20190104170802.4ed27cce@hermes.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [96.45.36.15] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=fortinet.com; s=dkim; c=relaxed/relaxed; h=from:to:cc:subject:date:message-id:references:content-type:mime-version; bh=afeYkGtVHWoC9Wdt9Bi2pyns/01uxTxCSOJ6InSNQNk=; b=SvauSkiFeabwuuhCUbFprRtQDHExNoK27ds+flcqzLWfjuYRoWGepLUqz95F+6YXUmmYu9lpoDON 5fSiGAOtzGMp7VAAn1cnHsKx8rGtmbtmU3k1aBn2/jaYLTSGChTluyfIuaHbec6OLByIl4f+CL69 c8/YXKf4lVy4UYfOynkHRxHj858LNO76QTkhmK47OE5Oovt8/Y8tGwbPsPDtUqJGyv/yiyeK7nAf tS9TlDqCeJrnolSRQvKvDbHhD4MedCpRbILtgnQrxrFV/dmFjEN9B7ktovbpWsvjwbanBABZbrt8 5yGRCCt1Zwt9sZUQL3WtcrNiW4jxn5Gkl2W/ew== Subject: Re: [dpdk-users] Cannot run DPDK applications using Mellanox NIC under Hyper-V 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: Tue, 08 Jan 2019 18:38:44 -0000 Updates: many thanks for MLNX engineering team, doing the following can res= olve this issue: 1- On power shell: "Set-VMNetworkAdapter -VMName -Name "Network A= dapter" -IovQueuePairsRequested 64" 2- In the registry editor, make sure that you increase the ExtraVFsQuotas p= ercentage to be 1000 to use full resources.=20 HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Class\{4d36e97d-e325-1= 1ce-bfc1- 08002be10318}\\Parameters 3- BlockFlowsForPerformance registry key: HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Class\{4d36e97d-e325-1= 1ce-bfc1- 08002be10318}\\Parameters When the BlockFlowsForPerformance registry is set to 1, by default only L4 = rules are allowed to be configured with rte_flow API.=20 When the BlockFlowsForPerformance is set to 0, then L3 and L4 rules are all= owed. -----Original Message----- From: Stephen Hemminger =20 Sent: Friday, January 4, 2019 5:08 PM To: Liwu Liu Cc: users@dpdk.org Subject: Re: [dpdk-users] Cannot run DPDK applications using Mellanox NIC u= nder Hyper-V On Sat, 5 Jan 2019 00:35:13 +0000 Liwu Liu wrote: > Hi Stephen, >=20 > Yeah we are seeing all NETVSC, failsafe PMD, TAP, MLX4 VF. We are expec= ting bifurcation mode where default traffic goes with MLX4_EN slave to NETV= SC master to enter Linux net stack and certain flow-defined traffic shall g= o into DPDK RX queue rather than MLX4_EN net-dev queue. Unfortunately as we= cannot define flow into VF NIC, we cannot re-direct traffic into DPDK user= -land.=20 This is a little more complex. You need to use rte_flow on the failsafe PMD and that is supposed to get pr= opogated to TAP and MLX VF. The TAP PMD programs BPF in kernel, and the MLX VF PMD programs the VF flow= tables. Haven't tried it myself.