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 BB4A51B4CE for ; Sat, 5 Jan 2019 01:12:32 +0100 (CET) Received: from mail.fortinet.com ([192.168.221.213]) by smtp.fortinet.com with ESMTP id x050CWru017972-x050CWrw017972 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 4 Jan 2019 16:12:32 -0800 Received: from FGT-EXCH-MBX131.fortinet-us.com (192.168.221.131) by FGT-EXCH-CAS213.fortinet-us.com (192.168.221.213) with Microsoft SMTP Server (TLS) id 14.3.389.1; Fri, 4 Jan 2019 16:12:31 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com (192.168.221.132) by FGT-EXCH-MBX131.fortinet-us.com (192.168.221.131) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Fri, 4 Jan 2019 16:12:31 -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; Fri, 4 Jan 2019 16:12:31 -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/HLnTKOuGVPhM0hYtgAZRFKAABCTSUA= Date: Sat, 5 Jan 2019 00:12:31 +0000 Message-ID: <34e739bdcc804414af79921d12c3db96@fortinet.com> References: <20190104160647.7f17e932@hermes.lan> In-Reply-To: <20190104160647.7f17e932@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=sYKnjnN/+3wk/qVgU4docBLeSQ85h3wBL4MRjqz+xH0=; b=fxy1yb3XP6HUwR8+wdOhdKBqyJsgzsl4XWXlezev4amB77qOaFLTDpno+yT8ryFmPAC7wWrs9qrn ZcDkwdGjJ1wbp/22xihRC6CIdVr/1opJbJQ1qeKwsAwrAtv9on7vyDQAzzIxOp7UkfN+JqFcctTr JgRz7AGXT53KypdpRP8Ny7zLiYTRv2QwkLlwgox1iZ4oG0wB6yZjBVEKkUFan6eU0F9hIthVgCtk 1ZYp1u8xJeQz0TkNJFS4alFZpVr2DTirbFIAJDPgMmTZSLkCO4n2cTngRmug6MR+4bO3ZyCQDc8K kvI+83m9zZDqfBP9OLMXWiEVpXMMOUAVrxtYEg== 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: Sat, 05 Jan 2019 00:12:33 -0000 It is SR-IOV.=20 BR, Liwu -----Original Message----- From: Stephen Hemminger =20 Sent: Friday, January 4, 2019 4:07 PM To: Liwu Liu Cc: users@dpdk.org Subject: Re: [dpdk-users] Cannot run DPDK applications using Mellanox NIC u= nder Hyper-V On Fri, 4 Jan 2019 20:06:48 +0000 Liwu Liu wrote: > Hi Team, > We used to have similar problem for Ubuntu 18.04 hypervisor and resol= ved by set log_num_mgm_entry_size=3D-1. (Refer to https://mails.dpdk.org/ar= chives/users/2018-November/003647.html > ) >=20 > Somehow for Windows Servers with MLNX VPI, I do not know where to set s= uch and DPDK over MLX4 on linux vm has same failure of attaching flow. >=20 > [ 374.568992] __mlx4_ib_create_flow: mcg table is full. Fa= il to register network rule. size =3D 64 (out of memory error code) >=20 > Would like to get your help on this. It seems to be the case that the= PF interface is not configured to trust VF interfaces to be able to add ne= w flow rules. >=20 > Many thanks for help, >=20 > Liwu >=20 >=20 >=20 >=20 > *** Please note that this message and any attachments may contain confid= ential and proprietary material and information and are intended only for t= he use of the intended recipient(s). If you are not the intended recipient,= you are hereby notified that any review, use, disclosure, dissemination, d= istribution or copying of this message and any attachments is strictly proh= ibited. If you have received this email in error, please immediately notify= the sender and destroy this e-mail and any attachments and all copies, whe= ther electronic or printed. Please also note that any views, opinions, conc= lusions or commitments expressed in this message are those of the individua= l sender and do not necessarily reflect the views of Fortinet, Inc., its af= filiates, and emails are not binding on Fortinet and only a writing manuall= y signed by Fortinet's General Counsel can be a binding commitment of Forti= net to Fortinet's customers or partners. Thank you. ***=20 >=20 How are using the Mellanox device with Windows Server? PCI passthrough or S= R-IOV?