From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f179.google.com (mail-pl1-f179.google.com [209.85.214.179]) by dpdk.org (Postfix) with ESMTP id 497081B4C1 for ; Sat, 5 Jan 2019 01:06:57 +0100 (CET) Received: by mail-pl1-f179.google.com with SMTP id p8so18088990plo.2 for ; Fri, 04 Jan 2019 16:06:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=zUpKZi2pUmFeRkfOthsXdcTq+IuhPMz2PyiXB4L05RE=; b=K5PKedBtIhgFYF8y6Xhkn1BNoV4iIT0b8x2HSMyEpfYSqy50vIizXwA5jkEk+jW+v4 /ISTyNky0YMKPihDVCvBubzvX4t/VjUBIEnMyIQVEQJ7r5GXuzkSdV1uUr/H+a3HnpMA FzogdPPeX2AVmbI6nAJR+hRKtunpMe35wRSYyr32NuYN86pRP9AcKHBcp1joqq+GzNGo J7UnkTaioRR1vlm0eGeuxrkcOI5lJN7tnBE1Nkq93WA1xBRPSz0+Q+6ZXrM6IW3rjGxV B4E/sZZXJFTl+OHxzZTQxNLQCQpRX47gbwH/nsfuqicJFPol2hfT4Oi5OPmzH8nF5VE2 Jozg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=zUpKZi2pUmFeRkfOthsXdcTq+IuhPMz2PyiXB4L05RE=; b=Axw4GSufT/xnosyaaIhGeDsRYtf1WrS1vz4fL2oV9DL2ARAm89afLkXoyHRb2Waode cCCnR50Q2zG3M5wN5O9hnenc33nhC/HFVyf2Yf8TTsolihUtL21aQyOSJtA5NPGJvEss G1T22pLgAfiNPBDNoVotsi1wMBEzrbiICMf75F+Vp93mem1QOy2QvrfkxItTez20apkr 0aRYb221xDfuZqraI2hYSJ7rIYT9lb42ERmtAxBldjzy0+vcZsWZ2ZuivbULKw8yFnr3 VGbkrrlxirRAQZwHs4ARn/rGj7xe76VhSyfFW5rkhJvd2qBJO942jacXp2VkCJzQwTwc syiw== X-Gm-Message-State: AJcUuken43/rQwXtg/kGSRxT1/gcaIH6gouIHIo6G3iHXP5OcZrn/7Wy /Z8MSJKzc9YivgonQqjE1yBuNQ== X-Google-Smtp-Source: ALg8bN6elM1eYR+fu7xiFZjrAudRARYLoLd1+5AnIlX4a5iioJ3bCV5GDwwGbCmU0TFW7/bjnqR8jw== X-Received: by 2002:a17:902:aa8c:: with SMTP id d12mr53726555plr.25.1546646816262; Fri, 04 Jan 2019 16:06:56 -0800 (PST) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id k186sm44911229pge.13.2019.01.04.16.06.55 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 04 Jan 2019 16:06:55 -0800 (PST) Date: Fri, 4 Jan 2019 16:06:47 -0800 From: Stephen Hemminger To: Liwu Liu Cc: "users@dpdk.org" Message-ID: <20190104160647.7f17e932@hermes.lan> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:06:57 -0000 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 resolved by set log_num_mgm_entry_size=-1. (Refer to https://mails.dpdk.org/archives/users/2018-November/003647.html > ) > > Somehow for Windows Servers with MLNX VPI, I do not know where to set such and DPDK over MLX4 on linux vm has same failure of attaching flow. > > [ 374.568992] __mlx4_ib_create_flow: mcg table is full. Fail to register network rule. size = 64 (out of memory error code) > > 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 new flow rules. > > Many thanks for help, > > Liwu > > > > > *** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. *** > How are using the Mellanox device with Windows Server? PCI passthrough or SR-IOV?