From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f42.google.com (mail-it0-f42.google.com [209.85.214.42]) by dpdk.org (Postfix) with ESMTP id 3D1A32030 for ; Wed, 13 Dec 2017 13:53:43 +0100 (CET) Received: by mail-it0-f42.google.com with SMTP id b5so3680307itc.3 for ; Wed, 13 Dec 2017 04:53:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:cc; bh=HCdc2htl70xajgQHo48hiLBukwAYJEcHkYOoUIpHAc4=; b=BiY5ODbqsAdaX+9jkRpxiAxw0M3qqtSNqhXyKbx+uLUq8qhnptjWsx9rtd2dYyGrDr aaD0KR9LycRrri9utGwF0rvSbjpauRC6sVaTPFNvyC2c4YXD3YnwaxV2eazjBgATwKCl mMyqRoenGnJ1wj8uCQWpJEJ4hXdISnV1QNukoZbj1juuLV9+vmXkrDMEMx4khdXPA5xX cG+XF4M2OzHL6dMjAHRxk35zjgG7zY3t2zMOMUpRBZrFDxKeSS9YhSQVcHpfohwhnWJg MbVj+3ShihqZhm1ufUfqrYiz9e2lSGZ3ex6fGf0xz2oUcKFmK5IIzvKER51JD/eful5J tVew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:cc; bh=HCdc2htl70xajgQHo48hiLBukwAYJEcHkYOoUIpHAc4=; b=t7S+IHHoNd1DwBCz65djGNTAyiKGKFX/r7gKjEEfbm/ncPuD4L/bCXRJJUnzEOjlV0 RRuk/3UCpY6kQ9HOrPb8lbO2CTymQhb8rvUSc7nkxc2nKkS606XgdP4Ouy/+qUDMlZX9 4QMbVQZSfm6JhhrAPT4ky6bui3Ftv1ADffPoQAZ2DezwjBbSxYC23ZF99S5Nee2XyLI3 laPXyiqXNuZJwmlSZ/pjzKVecsdzvswdwiTP+JUMEAID7wX1p32MSBimOJ3EKUKxO8kv PNb8T7s0ewLWwyGapCce4DtjPLiKgECpHcURo0t9XTJsgXRblKtvsm+UYNUklztgTvzW a6WQ== X-Gm-Message-State: AKGB3mKn1rFyv05nyD4Jcj/XANYhHfrVj9e7b3nf7T02OJk71TFvI7BI RVKjx5FgZAU2Ei1Hno2fA3bBt1pS2/P/tmDuux2H7w== X-Google-Smtp-Source: ACJfBovzNYvYQo/clWNJg1wzTft72oA2cl0KuP+/KIM7Uq5PLjD+otdGcWGd/eyIFkcO/8mcGazPM7j74stmWCHJ6A4= X-Received: by 10.36.86.3 with SMTP id o3mr2870144itb.18.1513169622292; Wed, 13 Dec 2017 04:53:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.144.139 with HTTP; Wed, 13 Dec 2017 04:53:41 -0800 (PST) In-Reply-To: References: <74DD2809-CE00-4CFD-8675-D27636EC3FC2@net.in.tum.de> From: ".." Date: Wed, 13 Dec 2017 13:53:41 +0100 Message-ID: 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 Reply-To: hyperhead@gmail.com List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2017 12:53:43 -0000 Hi, sorry the ignored comment was a bit brash. Its my first time posting, and I didnt see the email I sent come into my inbox (I guess you don't get them sent to yourself), so I did wonder if it posted ok. However the list archives showed that it did. Thanks On Wed, 13 Dec 2017, 13:20 .., wrote: > 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 >> queue. >> >> 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 >> 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 para= m >> >> 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 = 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 >> >> >> >> -- >> Chair of Network Architectures and Services >> Department of Informatics >> Technical University of Munich >> Boltzmannstr. 3 >> 85748 Garching bei M=C3=BCnchen, Germany >> >> >> >> >>