From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9384DA0A02 for ; Fri, 15 Jan 2021 07:09:38 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3776C140EF0; Fri, 15 Jan 2021 07:09:38 +0100 (CET) Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) by mails.dpdk.org (Postfix) with ESMTP id 94303140EEA for ; Fri, 15 Jan 2021 07:09:36 +0100 (CET) Received: by mail-io1-f47.google.com with SMTP id r9so16115845ioo.7 for ; Thu, 14 Jan 2021 22:09:36 -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=TuGYREuNpv/Q9Yz1gZpvQo92Cnif+21RstDfkejlPZA=; b=M+/rpYVoKJxz9RIMW75ndX7Q6zcq5iMV0GJd5OCfMpIf4h7P58+sIiMNxX+na5lXLy CwXTkZqVikoPx1DLDZPUhlc16/ls9QFUvkIFBatnsAW1F2uB6Ngwv0bNVxgWRMMLbFV0 vKmi3whk8bn5xrguCtEhuGnazX6HRDjeRNtvin3pXO7/sldTOaaNzP1RpCYQFs1/NCQf OgIplVzmmeznTJmu9c/B4F+EwKRC019i1Xo0wmjZfGQlzoDMtWLQVZ0KSmMCS5ryL0RC Ps6FD3QV1DhrLjREteYoOqRuNN/ISc/9QNXv4AwF0hgPqxVIUvL6tqUL3XTPpJIkyWLt HW1g== 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=TuGYREuNpv/Q9Yz1gZpvQo92Cnif+21RstDfkejlPZA=; b=Vi7nucUPWgmV0QJAr5HiLO9CeTMGiQxQRINdw17ayzjIEZS8hbB0/31wzue25k4yIO j3egR6afQjw/sYZD4Tmt3Hu1/HIwENmfv4ixhcfnhzmJk1nbb0NtiQjacXTDQOuQ6Wcz a5DsCgpXBtugZfmpm2ZjrET3dJQnYLk1PU2vzl3uAckwU3kynzVszWgaNukHtUwOiX3h GgNn1dz2gk5eqwott1XyDqeneHm+hNDoEwCOGwteswJCloX50GFi6arcRpMUqkqaEBng dFoh2RpHmuRH2kPJ1HXjlnN0CVUTLVS/s72XAbXkioJvh7ws60OkQZ9/coqmyzYOaXmP Ur1g== X-Gm-Message-State: AOAM532KU7RpGQUzsznlS7DpHqxpFqqXERUNDkYzj5fpZ0K4gBPlx5/C RASkWZpGkXI8f3O0qqZ/2UYcXNT1haagsSYFiwQ= X-Google-Smtp-Source: ABdhPJzUCFWgd+U/bwkbUqK3cKwuynwckeFUZPFwgGCxS/agVFjx33ViptUuR+zJ2nwcMPLLg0YlKYyB0/8mj/2ZXuo= X-Received: by 2002:a6b:b2c3:: with SMTP id b186mr7404734iof.126.1610690975876; Thu, 14 Jan 2021 22:09:35 -0800 (PST) MIME-Version: 1.0 References: <9703725.R88ScZ5S0C@thomas> <73D78AF1-8DEB-46A9-8A5A-E32AF48B2F30@vmware.com> In-Reply-To: <73D78AF1-8DEB-46A9-8A5A-E32AF48B2F30@vmware.com> From: madhukar mythri Date: Fri, 15 Jan 2021 11:39:24 +0530 Message-ID: To: Yong Wang Cc: Thomas Monjalon , "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-users] Does vmxnet3 PMD supports LSC=1 ? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi Yong, Thanks for quick response. As per "vmxnet3" PCI bus device information, we got MSI-X based interrupt-line as mentioned below in the "sysfs": we are able to get link-changes interrupts, but, on top it we get all other interrupts also, which is taking more CPU-time when traffic load. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ~ # cat /sys/bus/pci/devices/0000\:03\:00.0/msi_irqs/58 msix ~ # ~ # lspci -s 03:00.0 -vv 03:00.0 Class 0200: Device 15ad:07b0 (rev 01) Subsystem: Device 15ad:07b0 Physical Slot: 160 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR- wrote: > Vmxnet3 driver supports lsc and your observation is a known behavior with > vmxnet3 running with INTx/MSI interrupt mode. Enabling or disabling lsc > intr in this mode will enable/disable RX interrupts as well. This is a > device behavior and there is no known way to mask just lsc or rx interrup= ts > as the mask is per vector. To work around this, either disable interrupt > or move to msi-x. Currently the upstream dpdk vmxnet3 driver does not > support msix. We have plans to upstream vmxnet3 msix support in the futu= re. > > Yong > > =EF=BB=BF-----Original Message----- > From: Thomas Monjalon > Date: Thursday, January 14, 2021 at 10:50 AM > To: madhukar mythri > Cc: "users@dpdk.org" , Yong Wang > Subject: Re: [dpdk-users] Does vmxnet3 PMD supports LSC=3D1 ? > > +Cc Yong Wang, maintainer of this PMD. > > 14/01/2021 18:30, madhukar mythri: > > Hi, > > > > Does vmxnet3 PMD support LSC=3D1(i.e with interrupt mode) for link > changes ? > > > > When i enable LSC=3D1 the functionality works fine, but, when pumpi= ng > traffic > > i'm seeing increasing in CPU load on some cores which is running > > "eal-intr-thread" epoll_wait() function for more CPU-time. > > > > Actually, interrupt should come only when Link changes, but, we are > seeing > > interrupt for each incoming Rx-packet and also a lot of spurious > interrupts. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > ~ # cat /proc/interrupts |grep igb > > 58: 1254293 0 0 0 PCI-MSI > 1572864-edge > > igb_uio > > 59: 1278105 0 0 0 PCI-MSI > 5767168-edge > > igb_uio > > ~ # cat /proc/irq/58/spurious > > count 98035 > > unhandled 0 > > last_unhandled 0 ms > > ~ # > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > Does anyone tried LSC=3D1 in vmxnet3 PMD based apps and faced simil= ar > issues > > ? If so, please let me know. > > > > Tried with DPDK-18.11, DPDK-19.11 and DPDK-20.05. > > > > Thanks, > > Madhukar. > > > >