Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp3027932ybe; Sun, 8 Sep 2019 05:44:51 -0700 (PDT) X-Google-Smtp-Source: APXvYqwScndr+BbygUM0kJnwbcGbrnoMBAgkNz3bE7LyO1KGLhFZ73xjSRJ8F1niir9czT2sCvYd X-Received: by 2002:a05:6402:1598:: with SMTP id c24mr19118408edv.174.1567946691311; Sun, 08 Sep 2019 05:44:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567946691; cv=none; d=google.com; s=arc-20160816; b=EV38RVa4jFJRVzhaQaE0kehZ6c8EFsUZpvseltQrKEpVDEvogD7+hRtOR7MDm6islM gNVbC0tiTeTOesErSmNxQzHxVfPPpuuPGClzKd1g1jQdpWQe63L/R/HgHGZyGfGgnvTM lWRl4gL3dKdNkboITiU+9fqH7+40qr0WU8VJSzohg5Y5klwViWbhr//sD2ZJ1AnD00rj bN8NA/wARgCTIBHV1EgkxfZTh5TT/R/Hti6R5tj6bLQZVqeZ5TCTjseKKkP0GrgxF88S hde0b/d3TF+I/oGlZOBQF1iQrXAWDrYXuAy3oSL+Aer5KxoMBMQyxhlo7TyOvex+QdDV wfKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=uRpzcGRK0gWOk89qrLh7rcTqBiKXyCtjzVPSfOAgpVU=; b=Dt5N0mcqF26uSdkyEQv8dvb/874B1ZTEBUQ3gjeZRLa7VQ2ZQx0JYPqkClP9bbPvvp m7XV5qgpx79TlzUw9ZPyD2Wtp/07Kzo2EgOsdl0sUQ5+mFKG+T7l4qM8+06B5kQwHA97 sh6r6S1Z9fmZ1CWU7fNypQZ+fJn0uBbAOmAU6BUxUyT4NBbNXzPSaTFfLDxtOBA5A4VK 8hS9Fe6h2ZFfmbPTVG6QVi7iNR/WoqC18E4lNJLb4AH9egztE/LrOkXHmYjCuBeSiiMm TQQmpazmXwWzuvhrJati4uhnvPS+RmBTILMfDgBY2h6iEJbCRjqxYt9QDYmgpIN+dYa3 49/w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@netronome-com.20150623.gappssmtp.com header.s=20150623 header.b=etwCiax2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e46si6660273eda.401.2019.09.08.05.44.27; Sun, 08 Sep 2019 05:44:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@netronome-com.20150623.gappssmtp.com header.s=20150623 header.b=etwCiax2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405741AbfIGE03 (ORCPT + 99 others); Sat, 7 Sep 2019 00:26:29 -0400 Received: from mail-pl1-f195.google.com ([209.85.214.195]:46213 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404319AbfIGE02 (ORCPT ); Sat, 7 Sep 2019 00:26:28 -0400 Received: by mail-pl1-f195.google.com with SMTP id t1so4111120plq.13 for ; Fri, 06 Sep 2019 21:26:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netronome-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=uRpzcGRK0gWOk89qrLh7rcTqBiKXyCtjzVPSfOAgpVU=; b=etwCiax2gYdlC4zP7k7KvjURjCrgAs+KXsRggYDRDUSymUUnwC/2d3q8vjQwUWtudw OSlZL4GgcgosbLef5+vO8HsQSFba21KpO+8TzzlB/xLI3mkZrv+qC2MyzRbX7/DW00VY 1qJWdUbMv87N3RbQ7gkM8xgBTX7pTUwAHsH9SqiluIV2b+uU71JYYmisQZF0IK6RZVhl jNNaJOoj9OaJUZFwrOJRkY6emDZTA6RBNSIW2IYqQ1G/Si/2hEo5Vdp1YviTIyBQDa/B sW9vwo5ucxzgbZynOtDN0nB2u3aQ5+5pT8Ftz7eALy7+EGvelHsKuetu+FVTbcoYlNwu IilA== 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:organization:mime-version:content-transfer-encoding; bh=uRpzcGRK0gWOk89qrLh7rcTqBiKXyCtjzVPSfOAgpVU=; b=aLizTaC276i1PpICUj4LhP8f8QU4LdeCPujl9f/jNcVqXUuNDBLS19gYUlj1yfMq3F BlJixMCdqxC7MNRglGeQY9nhAFfwehofWUfN/Z3gT59ybgrC3J8R0SRP+6ecLBlP7hrx AJNkdVpa5RiqVhSgD+USnnRdg2e1b/NizY7ae3UNAiPf5ZV2G6JAfV8gpe0VQf6Ac5Hj i7KgYogOHkXJm9/8EY1A34afIfhQmt9qvVLOYsA7d8FQcLhaf9e4r37KSjSiazQxICt3 acvZOT12RaQOAn4/uIbOUqhIEqIGDbxuJdasTIT4naypmmLFdz2HAvcOOK1I2CmN2zTm WYww== X-Gm-Message-State: APjAAAWoilLnmxK7h85ZRSMfH1a9RVysw3maJ1dTMHqGH+0umFLG0KFn UfG+cmq7qeHf/BpGGXzXpnZXcw== X-Received: by 2002:a17:902:b215:: with SMTP id t21mr6431411plr.141.1567830387142; Fri, 06 Sep 2019 21:26:27 -0700 (PDT) Received: from cakuba.netronome.com ([45.41.183.19]) by smtp.gmail.com with ESMTPSA id z12sm7810845pfj.41.2019.09.06.21.26.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 06 Sep 2019 21:26:26 -0700 (PDT) Date: Fri, 6 Sep 2019 21:25:48 -0700 From: Jakub Kicinski To: Haiyang Zhang Cc: "sashal@kernel.org" , "linux-hyperv@vger.kernel.org" , "netdev@vger.kernel.org" , KY Srinivasan , Stephen Hemminger , "olaf@aepfle.de" , vkuznets , "davem@davemloft.net" , "linux-kernel@vger.kernel.org" , Mark Bloch Subject: Re: [PATCH net-next, 2/2] hv_netvsc: Sync offloading features to VF NIC Message-ID: <20190906212548.685b5f83@cakuba.netronome.com> In-Reply-To: References: <1567136656-49288-1-git-send-email-haiyangz@microsoft.com> <1567136656-49288-3-git-send-email-haiyangz@microsoft.com> <20190830160451.43a61cf9@cakuba.netronome.com> Organization: Netronome Systems, Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Sep 2019 23:07:32 +0000, Haiyang Zhang wrote: > > On Fri, 30 Aug 2019 03:45:38 +0000, Haiyang Zhang wrote: > > > VF NIC may go down then come up during host servicing events. This > > > causes the VF NIC offloading feature settings to roll back to the > > > defaults. This patch can synchronize features from synthetic NIC to > > > the VF NIC during ndo_set_features (ethtool -K), and > > > netvsc_register_vf when VF comes back after host events. > > > > > > Signed-off-by: Haiyang Zhang > > > Cc: Mark Bloch > > > > If we want to make this change in behaviour we should change net_failover > > at the same time. > > After checking the net_failover, I found it's for virtio based SRIOV, and very > different from what we did for Hyper-V based SRIOV. > > We let the netvsc driver acts as both the synthetic (PV) driver and the transparent > bonding master for the VF NIC. But net_failover acts as a master device on top > of both virtio PV NIC, and VF NIC. And the net_failover doesn't implemented > operations, like ndo_set_features. > So the code change for our netvsc driver cannot be applied to net_failover driver. > > I will re-submit my two patches (fixing the extra tab in the 1st one as you pointed > out). Thanks! I think it stands to reason that two modules which implement the same functionality behave the same.