From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 181A1A052F for ; Sun, 26 Jan 2020 22:20:35 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7D43449E0; Sun, 26 Jan 2020 22:20:34 +0100 (CET) Received: from mail-pg1-f180.google.com (mail-pg1-f180.google.com [209.85.215.180]) by dpdk.org (Postfix) with ESMTP id 342FE493D for ; Sun, 26 Jan 2020 22:20:33 +0100 (CET) Received: by mail-pg1-f180.google.com with SMTP id z124so4107344pgb.13 for ; Sun, 26 Jan 2020 13:20:33 -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=50EzUwp8mOfgXZsgp3mNBzo9yyxvyf3avCE3xXGR194=; b=voGEICrFRb1LtrbinM5cu2IWG0WqkHX94WNDCQsb7d421hCnyvjH6Yau8GbN3MmSI9 2Kb0BDwKzpP0vP/4WTxk6YmNDxuujybWgzQ0XKCywMnCQ3fqh3Pr+Z/9VCZjkqQo+WXy PgqgzhYtZahc/iSAn8vOmMpNq7MD4jII2U3E0fo6jQZo1HF+6THzCNddbp0L9RTpSACL q4iXNWzJ/sj804Uak8MRsiGjtpXTOmysZmM/+kbeHBSZereL+RrVxSyclV3nxQkfvqlF 40+8G41jOC3ewnTcY092W3xn3Gid5Ob3Vda7JQ5oRj7XNO9yhhlcJskJZi6akPxWnP1W RhNg== 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=50EzUwp8mOfgXZsgp3mNBzo9yyxvyf3avCE3xXGR194=; b=tNh0qbEeTqQpCJWfmrGfKXzJEajyhvAEkC5BrH6Z707LgsEtODALmwS1Z6SF+nkO1I RZJGieIfOzdIXH1SBrYQjVAXU8D+aVsOLv7su/4AmScYgMzvBRvdkj7oNaX83wWaMWm9 y4KwJqxdc55BTGRpB5bpioqqZRjmyF8vN7HznNsbHn2VwnGCgfQnd0jCShde0isXctYH whcTPTP7JWMi/tNQI2V443I+7MK6sEwVe8cQE1Iyf+UWUbBiRQcONVg2mMnfg8cVjM1O euiWcJECqacdETKv3R95ph/snIVwdMhamlqoyyewoFJx1zc/VI95VQNJ3mANEfk8tU2f eV/g== X-Gm-Message-State: APjAAAXw2NlU9fcfO+pnD0hpCBhgy7A2Oo+J+w6UfQFR6Nzuis+R2R8s hImdMbTimG/crToSxZ2M6l5N0wZZS9Y= X-Google-Smtp-Source: APXvYqwPxSsccHAewX6ws3V89NFW6+AHAIBQYHXyt4bSf3oAM9/jA/oM3KtOnWvxCieDCD6JpupE0g== X-Received: by 2002:a63:e34d:: with SMTP id o13mr15683215pgj.243.1580073631868; Sun, 26 Jan 2020 13:20:31 -0800 (PST) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id c1sm13075241pfa.51.2020.01.26.13.20.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 26 Jan 2020 13:20:31 -0800 (PST) Date: Sun, 26 Jan 2020 13:20:23 -0800 From: Stephen Hemminger To: Chris King Cc: users@dpdk.org Message-ID: <20200126132023.35a653a7@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] VPP / DPDK issue with failsafe adapters 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: , Errors-To: users-bounces@dpdk.org Sender: "users" On Thu, 23 Jan 2020 14:25:06 -0500 Chris King wrote: > Hello, > > I have been reaching out for support for a VPP / DPDK issue on the fd.io > forums here: > https://lists.fd.io/g/vpp-dev/topic/interface_activation_problem/69987045 > > Since my problem may be DPDK related (unsure) or at the boundary between > VPP and DPDK, I thought I would reach out here as well. > > Here is the latest context and any insights would be appreciated: > > Scenario: I am having difficulty getting my VPP interfaces activating > properly. I am trying to use DPDK-enabled netvsc devices with VPP in Ubuntu > 18.04 in Azure. > Recent versions of VPP decided to do a native Mellanox driver and no longer use the DPDK Mellanox driver. Since the native Mellanox driver is not visible to DPDK, the failsafe (and netvsc PMD) can not manage the devices. I got VPP working with failsafe and native netvsc PMD on earlier release of VPP. But the VPP developers decided that a native Mellanox driver would avoid the extra overhead of going from VPP to DPDK. In the process, they broke Azure. This is a VPP problem (they broke it, they need to fix it). There really isn't anything in DPDK that can be done to help. If VPP insists on doing their own Mellanox native driver, then they need to do their own native VMBus driver.