Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1586172ybh; Thu, 23 Jul 2020 12:38:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzmARE6cwoCIbzEQvNTrWcy+qlhB7SimNLpBqyqUEif67lw3X75+hL5Iao11xTexeQNJQKZ X-Received: by 2002:a17:906:c40d:: with SMTP id u13mr5742381ejz.519.1595533105837; Thu, 23 Jul 2020 12:38:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595533105; cv=none; d=google.com; s=arc-20160816; b=tvhBadpMb+TdaBKWGa+qaKNrOG1L7XdFy0GeW2QAsC9xFTMnOluzBIocJ7+vXvrEHN +BzFLBAASjrde2qAkXHK1ixdNQOapazwvQA3zrqJzYbGuj4Tc6IWEdTS6cd8VuWixZ7S WasTF3lbtREnS82nSuNZ++qMt8uafN1ALShKQqsnLd7l7EiaaNUX815L9gi6X9fJP2Nx IONX8uilAnevnp3/PhH9V4518AA7S4qMY8fOu0e1PMeO1VuF6E2OT8LCILvxDQTO0lL4 8Q/sjNZvLJB7jM7m61CF7Cj9hGRnD1bhV8410LozorH7cKzMaDyzc4HFk1lAWiWGsVUZ SibA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=2nbc3N138GdZ1RuKmdAQEB7Zo4IYK54+HxVgjYpwRo8=; b=KQp1PUSGeDm3OMGTlov02ICz1GQU8d+CQVhhaf0+Dj/5WNtlQyFvZK3FpGmKJt1RYT n4zHI2tIMHNzTjdVxsgzKqS6PgVHks9q3vC382cxuwf6oTnR5JKWFw1vZ5T/75B1IlyN N7PtIKJvKsnqYmTkZ2WDq1eukknQMFPoz/jiflYFC88Fh1kBPDxOMilpgrRNXTEIBLLg 1yuh9unzF/day/nM4Hpr4obMjzcwkOvbM89v7/gvH+bkVf4GXP4GHvnGfu/nJyXZeYVq UmmE3qLTu6K+gJbjmQbjMksBvw9IFL43elnf3Ki0NJDneMtVir8vGugXdmPuQxk3pVRV qIog== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 90si2649534ede.250.2020.07.23.12.38.01; Thu, 23 Jul 2020 12:38:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726379AbgGWTfo (ORCPT + 99 others); Thu, 23 Jul 2020 15:35:44 -0400 Received: from mx2.suse.de ([195.135.220.15]:53050 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725894AbgGWTfo (ORCPT ); Thu, 23 Jul 2020 15:35:44 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id DCBC3AB89; Thu, 23 Jul 2020 19:35:50 +0000 (UTC) Received: by lion.mk-sys.cz (Postfix, from userid 1000) id 5C59B604C9; Thu, 23 Jul 2020 21:35:42 +0200 (CEST) Date: Thu, 23 Jul 2020 21:35:42 +0200 From: Michal Kubecek To: Chi Song Cc: "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , Wei Liu , "David S. Miller" , Jakub Kicinski , linux-hyperv@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v7 net-next] net: hyperv: dump TX indirection table to ethtool regs Message-ID: <20200723193542.6vwu4cbokbihw3nh@lion.mk-sys.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 22, 2020 at 11:59:09PM -0700, Chi Song wrote: > An imbalanced TX indirection table causes netvsc to have low > performance. This table is created and managed during runtime. To help > better diagnose performance issues caused by imbalanced tables, it needs > make TX indirection tables visible. > > Because TX indirection table is driver specified information, so > display it via ethtool register dump. Is the Tx indirection table really unique to netvsc or can we expect other drivers to support similar feature? Also, would it make sense to allow also setting the table with ethtool? (AFAICS it can be only set from hypervisor at the moment.) It kind of feels that the actual reason for using register dump was that it's there and it was easy to use rather than that the information would logically belong there. We already have a specific interface for getting and seting receive indirection table; perhaps it would make sense to have also one for the transmit indirection table. Michal