From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 8BD359FE for ; Wed, 13 Dec 2017 12:26:24 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 136A4208B8; Wed, 13 Dec 2017 06:26:24 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 13 Dec 2017 06:26:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=1AKnjiY+Y8JiDkgCfndm8O9W99 EJhwtPXF5EzNEkbAs=; b=pk/QwshYPsq51jj5TPPrzqgzbycaZi6MrbJLF5Cj02 y0H9fekUKNbT3C8fWsM33XfH9G91GEDZXgR8UdAuKk/MELnrIMj2JnkqkmNfWvEk fWi2OsjWcgPE7dIwfldcj598eEVKyta3x/+2u1ZrXkaL2rRe1bDyX0ZKAq1734dW w= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=1AKnji Y+Y8JiDkgCfndm8O9W99EJhwtPXF5EzNEkbAs=; b=Rzbl+fcdVNJMDzdPCgPhzw 63qMnYlY/Vq6/Do1Xb3c0FkM0A2UWWG8292stcWkR9G8NIAlKOqV5p5QZmeCEerK t2661n7j06QKGnZRKY2UtkzsMN1nkuHWCs7ltq0zd3xZ1bIfrpWo2A02pzAcDy0B vpyKmgVklTje4Gr4WI+76fITzVPkEoBs7AqeEgwrrT+4hFTX/5Pyx+RZmWBdKTz/ qH2Zbd5RCuIHSuO3Ir9Bi5NN0uNjpyCH89Ed+LSOw0Kxza4L4MIhvIEAJZ6ONrKA ZyyHvN5+924K34TPFi9vTdW2CUcCnTlprgGpYE3pE6NvZN7P1yG4yLKDDGvJ9+AQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B4E1A2415E; Wed, 13 Dec 2017 06:26:23 -0500 (EST) From: Thomas Monjalon To: hyperhead@gmail.com Cc: users@dpdk.org, Wenzhuo Lu Date: Wed, 13 Dec 2017 12:26:22 +0100 Message-ID: <1611603.KVu9l4JnOr@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-users] VF RSS availble in I350-T2? 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: Wed, 13 Dec 2017 11:26:24 -0000 12/12/2017 13:58, ..: > I assume my message was ignored due to it not being related to dpdk > software? It is ignored because people have not read it or are not expert in this hardware. I am CC'ing the maintainer of igb/e1000. > On 11 December 2017 at 10:14, .. wrote: > > > Hi, > > > > I have an intel I350-T2 which I use for SR-IOV, however, I am hitting some > > rx_dropped on the card when I start increasing traffic. (I have got more > > with the same software out of a identical bare metal system) > > > > I am using the Intel igb driver on Centos 7.2 (downloaded from Intel not > > the driver installed with Centos), so the RSS parameters amongst others are > > availbe to me > > > > This then led me to investigate the interrupts on the tx rx ring buffers > > and I noticed that the interface (vfs enabled) only had on tx/rx queue. Its > > distributed between This is on the KVM Host > > > > CPU0 CPU1 CPU2 CPU3 CPU4 > > CPU5 CPU6 CPU7 CPU8 > > 100: 1 33 137 0 0 > > 0 0 0 0 IR-PCI-MSI-edge ens2f1 > > 101: 2224 0 0 6309 178807 > > 0 0 0 0 IR-PCI-MSI-edge ens2f1-TxRx-0 > > > > Looking at my standard nic ethernet ports I see 1 rx and 4 rx queues > > > > On the VM I only get one tx one rx queue ( I know all the interrupts are > > only using CPU0) but that is defined in our builds. > > > > egrep "CPU|ens11" /proc/interrupts > > CPU0 CPU1 CPU2 CPU3 CPU4 > > CPU5 CPU6 CPU7 > > 34: 715885552 0 0 0 0 > > 0 0 0 0 PCI-MSI-edge ens11-tx-0 > > 35: 559402399 0 0 0 0 > > 0 0 0 0 PCI-MSI-edge ens11-rx-0 > > > > I activated RSS in my card, and can set if, however if I use the param > > max_vfs=n then it defaults back to to 1 rx 1 tx queue per nic port > > > > [ 392.833410] igb 0000:07:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 > > tx queue(s) > > [ 393.035408] igb 0000:07:00.1: Using MSI-X interrupts. 1 rx queue(s), 1 > > tx queue(s) > > > > I have been reading some of the dpdk older posts and see that VF RSS is > > implemented in some cards, does anybody know if its available in this card > > (from reading it only seemed the 10GB cards) > > > > One of my plans aside from trying to create more RSS per VM is to add more > > CPUS to the VM that are not isolated so that the rx and tx queues can > > distribute their load a bit to see if this helps. > > > > Also is it worth investigating the VMDq options, however I understand this > > to be less useful than SR-IOV which works well for me with KVM. > > > > > > Thanks in advance, > > > > Rolando > > >