Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp2719802pxk; Mon, 14 Sep 2020 23:46:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwuE8j5JtURJ2E9gg2/JluQhIm1dEI3D09DXSVnXEw9aOixzsPf+wQ55JALY+zYf0LoP9wz X-Received: by 2002:a17:906:f1cf:: with SMTP id gx15mr18099186ejb.241.1600152405403; Mon, 14 Sep 2020 23:46:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600152405; cv=none; d=google.com; s=arc-20160816; b=OXxKEauHCjibml+QvtXwyj5yKUkTsT8Z2rSQXF1OIHtsxlbV/AOomANptsxRpv0ULp Xbe3vRe+A4xjK7/krV+Lw8l7yOOSmZOFn9ovO870rCNMmML2+Q4mE6mQealBTJA+i14O MFNdGCOc5GbyRchsBkMMNPS6ZPyTgwNQzdO7TT1L6jc/mAjMOD8LEZd0UGg8h7Kqb3SB QdId1qnhXbSMX+QxC8kooO2f51XXQq/fc23xIA4DHwQsnTIc//3YZa93etANqmONvvDU S2uh3GoKst25RuXua4/nkMVeEhfncHMFOwVXgAwqF2v9xvuxpRA7IT9XvRpH1A9Sue1Y O7KA== 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 :dkim-signature; bh=GldgJ7RQPmzPgW3JiwuzicyOz0XVLdYlzL3wC9ojd4w=; b=m329XbiDKKarf8HFsBsu1g1Ah86p7557VTGOPY5f1PijRlR4E6GF4EwAlLtJZNUgc+ vIIOqqzzcIR/pc6thoPbNA/pk6ZaLW9bIP72Quh0DyPXQJfXSaL7I1y6gv9HiNLAYP9R ZFQ1kKn4t1CyvkLoaq8VFtSankDqBu/JncxCmHE2DbaCk1EChGCSQYKQO/djb+We1y9x UlKzRMCdXNkOuIUoBYWFrpyoqk/DOQPxyEHB+Ul1GRIb4QgOMZ4W7nMeASRgFt07hwVC hTTmPTEygau2j28w+mhUB2vdaHDpAaLxhgbfyGlEbimzmbzORnE1+Xk+G1GuIYBvN8GC 3b5w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=hcTuqWy7; 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 b15si558818ejk.84.2020.09.14.23.46.22; Mon, 14 Sep 2020 23:46:45 -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; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=hcTuqWy7; 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 S1726125AbgIOGpc (ORCPT + 99 others); Tue, 15 Sep 2020 02:45:32 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:37569 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726033AbgIOGp1 (ORCPT ); Tue, 15 Sep 2020 02:45:27 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 699F95C00C1; Tue, 15 Sep 2020 02:45:25 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 15 Sep 2020 02:45:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=GldgJ7 RQPmzPgW3JiwuzicyOz0XVLdYlzL3wC9ojd4w=; b=hcTuqWy7erNiktGtVzF8uP 2YL10NlcSzn5r+EdNUIaZwz5Hs7LNwOdowplGemJ5xX8IAN/vjFE0/7/DlAW4H9z goSBFgm9C3AWQtwdv+cqF244avZaYMTD8MGtEaz2tYGCL4rjSp1jd8tHa5a13zr8 0AQu1QE76f0aAgnc/fcTSJv7kZHPuX2xL2zD3CTTRJ5BFS89eFUHnFMGJM9P96lI ioTD7SspJBys6y5AHo2ZjZNn9+VYkQHjKYHOlRAs6CMeZQL1F9Hr5QhouZxC0qAs V4SbCnyjJGtyuSzm7p+3T0M6wQy4rU2LLV7VQh+DRloaCXXhKXhd+sIWPxUuhJiw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudeijedguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepkfguohcu ufgthhhimhhmvghluceoihguohhstghhsehiughoshgthhdrohhrgheqnecuggftrfgrth htvghrnhephefhtdfhudeuhefgkeekhfehuddtvdevfeetheetkeelvefggeetveeuleeh keeunecuffhomhgrihhnpehgihhthhhusgdrtghomhenucfkphepkeegrddvvdelrdefie drkedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep ihguohhstghhsehiughoshgthhdrohhrgh X-ME-Proxy: Received: from localhost (igld-84-229-36-82.inter.net.il [84.229.36.82]) by mail.messagingengine.com (Postfix) with ESMTPA id EB9FF306467D; Tue, 15 Sep 2020 02:45:21 -0400 (EDT) Date: Tue, 15 Sep 2020 09:45:19 +0300 From: Ido Schimmel To: Jiri Pirko Cc: Moshe Shemesh , "David S. Miller" , Jakub Kicinski , Jiri Pirko , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next RFC v4 04/15] devlink: Add reload actions stats to dev get Message-ID: <20200915064519.GA5390@shredder> References: <1600063682-17313-1-git-send-email-moshe@mellanox.com> <1600063682-17313-5-git-send-email-moshe@mellanox.com> <20200914134500.GH2236@nanopsycho.orion> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200914134500.GH2236@nanopsycho.orion> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 14, 2020 at 03:45:00PM +0200, Jiri Pirko wrote: > Mon, Sep 14, 2020 at 08:07:51AM CEST, moshe@mellanox.com wrote: > >Expose devlink reload actions stats to the user through devlink dev > >get command. > > > >Examples: > >$ devlink dev show > >pci/0000:82:00.0: > > reload_action_stats: > > driver_reinit 2 > > fw_activate 1 > > driver_reinit_no_reset 0 > > fw_activate_no_reset 0 > >pci/0000:82:00.1: > > reload_action_stats: > > driver_reinit 1 > > fw_activate 1 > > driver_reinit_no_reset 0 > > fw_activate_no_reset 0 > > I would rather have something like: > stats: > reload_action: > driver_reinit 1 > fw_activate 1 > driver_reinit_no_reset 0 > fw_activate_no_reset 0 > > Then we can easily extend and add other stats in the tree. > > > Also, I wonder if these stats could be somehow merged with Ido's metrics > work: > https://github.com/idosch/linux/commits/submit/devlink_metric_rfc_v1 > > Ido, would it make sense? I guess. My original idea for devlink-metric was to expose design-specific metrics to user space where the entity registering the metrics is the device driver. In this case the entity would be devlink itself and it would be auto-registered for each device. > > > > > >$ devlink dev show -jp > >{ > > "dev": { > > "pci/0000:82:00.0": { > > "reload_action_stats": [ { > > "driver_reinit": 2 > > },{ > > "fw_activate": 1 > > },{ > > "driver_reinit_no_reset": 0 > > },{ > > "fw_activate_no_reset": 0 > > } ] > > }, > > "pci/0000:82:00.1": { > > "reload_action_stats": [ { > > "driver_reinit": 1 > > },{ > > "fw_activate": 1 > > },{ > > "driver_reinit_no_reset": 0 > > },{ > > "fw_activate_no_reset": 0 > > } ] > > } > > } > >} > > > > [..]