From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f41.google.com (mail-it0-f41.google.com [209.85.214.41]) by dpdk.org (Postfix) with ESMTP id 99771200 for ; Wed, 13 Dec 2017 13:24:39 +0100 (CET) Received: by mail-it0-f41.google.com with SMTP id 68so3373713ite.4 for ; Wed, 13 Dec 2017 04:24:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yGSK2+YYSIzkAHg0bm/52B+gpuccRMjmtbu+Zjq6IoE=; b=F2HIPij9+BxivnzvkUJs9JhpRH4j+q27PN9jZd4TW5B1SIvd0Krk+Zwm65hfrdcQit cdFZDT9O0iR91iITFpuMdyzrb3kZePLNY6NzSBlxPotKqN/ueC0vDmSDo/Lz5sX3Qha6 2v/ATp3BocztqNwFXLD16Q0eqEvj+STwwjQ1cI19eMPspMZXtxvtvcrUq/rr2Q9854hS BGqjKbkLwCr9/zLGmzLISicT110Mx6P0jATsQV7TCG/bnG3JdqZ1X9J9BIf2dBWz3zME JwuD73qQbVdGxZcppOtm4romlxb8wfQ0lTgg4eewZ1jaMYxcBTP1PGdjAx9XE17JVBEa xGWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yGSK2+YYSIzkAHg0bm/52B+gpuccRMjmtbu+Zjq6IoE=; b=sd/0mLaHfhSCzfem1d2d1NJ7K0og+MkO2T/hFPjTU/wMHHVPJ4g57DrhvOoE7TnE3m tzbk+zB/gWq1sP0SA2/S29jNL4831qTgVilFCFRQbWQMqpPb6koGgsCROigtGXFDVzQf usUJbH4sMJbXSsR+TJvxWjbebbYzULUTte38sNCZ5mPmKJ21c5D9eqi13wUDORvD8PdM hWtbUR6aRHcOxKkAD+cwqO9CJMlWrRBTWJY5G3OOWIYt5/BOM4lh1WY1xWjo7Glmor9y 7wUY5dPjCsEGJ5AN+4uB/sHvUx1ZMhMpFWlVgqdRu+1xHYGO4mxaEm6l5Ec3Ze+KzWC9 vq1w== X-Gm-Message-State: AKGB3mKuGfwFvNoWu1KAJuKjJs5pt7q6ZuCG5sa/6xvk9q/FQwi89gOA lJB3ecaUj+vmWvpN351Em514Jl93u2JNLCCHrVxJPA== X-Google-Smtp-Source: ACJfBosNeJaxHJocfF4Kr5F+/oVVwAl7azD5D+MdTobibFR/l6mo9EUk29+wV+A6GtQIRLD3Jeljwvk1v4Z/aWsBeSU= X-Received: by 10.36.70.146 with SMTP id j140mr2906351itb.66.1513167878772; Wed, 13 Dec 2017 04:24:38 -0800 (PST) MIME-Version: 1.0 References: <74DD2809-CE00-4CFD-8675-D27636EC3FC2@net.in.tum.de> In-Reply-To: <74DD2809-CE00-4CFD-8675-D27636EC3FC2@net.in.tum.de> From: ".." Date: Wed, 13 Dec 2017 12:24:28 +0000 Message-ID: To: Paul Emmerich Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 12:24:40 -0000 Hi Paul, No I didn't spot that. I guess my only option now is 10gb card that supports it. Thanks. On Wed, 13 Dec 2017, 12:35 Paul Emmerich, wrote: > Did you consult the datasheet? It says that the VF only supports one queu= e. > > Paul > > > Am 12.12.2017 um 13:58 schrieb .. : > > > > I assume my message was ignored due to it not being related to dpdk > > software? > > > > > > 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 mo= re > >> 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 n= ot > >> the driver installed with Centos), so the RSS parameters amongst other= s > are > >> availbe to me > >> > >> This then led me to investigate the interrupts on the tx rx ring buffe= rs > >> 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 a= re > >> 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=3Dn 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 i= s > >> 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 > >> > > -- > Chair of Network Architectures and Services > Department of Informatics > Technical University of Munich > Boltzmannstr. 3 > 85748 Garching bei M=C3=BCnchen, Germany > > > > >