Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp45966pxb; Tue, 10 Nov 2020 19:18:39 -0800 (PST) X-Google-Smtp-Source: ABdhPJySTqfkg75DjYOkhi20CLvjxc12vfgksQH1ZhQocId/9Z2EnDhjngNlwM+0Y/+w7XLhdfUB X-Received: by 2002:a17:906:17d6:: with SMTP id u22mr10508894eje.399.1605064719659; Tue, 10 Nov 2020 19:18:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605064719; cv=none; d=google.com; s=arc-20160816; b=AxUlVE7qFL/0I5PcMMMz7bwcpIqMMcmEQWtqLXINwwChlXuvkpy39Q+0SUMpetpBDX v5HZQMekcGsXW7fQ9gktweMnuGzg8NoVVGSHMekKxVkaiiqm7Qseb3sNDszHA4e1OERC WiymbhTFt9+goAjROJTpYiKk4OknOitEQKpLDYMuL1zo+edbp6FaVBLUnPDXW0YL+yMn TzW8zEpcXgd952A5H4BRa33oyIxBiPCZA0CMsvz9r3L0xCOy4pn6mYTM/tLIjG1y/zm6 A83lJZTbvXp8j/VmSOGjM9yNeWozct0T7odg0xCyU7/Hsok2FgbpbnfiJdPu7HrVLmhD mZXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=sY3Qc98jZIED9Kn2EG8DxEx6C/PnF5J/cx7GAfKe3cM=; b=oaVGWCzLQ3e49ID31iLlEvRcs717zxO//5B7JBiqPIZhxv9n85+9s2m7p63Y5Dxh4m z1mxEOV890ySYzuEBV1llSJqubOIbC66fCwVLoMtngdi8e6shLBDyZ2/uQkGNyVAL0+S nUe9ZMGk6NXiwONsUDGcqf2+aRRw6+FTBJ1BXHm4PIJuRzg+zvwjdbHn81SWRzFjxb8n V6KCDJ1yjl5wFmCmT17MKjeP07BFUaUXCL4wzUW/qgEXth7YdwRdc878Ads29ZJ+HhFL viF+q4c4+JbfmLdz4YbqGTvG6rgASAteBIfxfBCzA3GkPbo52BCfTMe6ktRqtlXr8L4w CCOg== 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 q23si646422edb.127.2020.11.10.19.18.16; Tue, 10 Nov 2020 19:18:39 -0800 (PST) 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 S1725945AbgKKDQt (ORCPT + 99 others); Tue, 10 Nov 2020 22:16:49 -0500 Received: from szxga07-in.huawei.com ([45.249.212.35]:7878 "EHLO szxga07-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725867AbgKKDQs (ORCPT ); Tue, 10 Nov 2020 22:16:48 -0500 Received: from DGGEMS404-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga07-in.huawei.com (SkyGuard) with ESMTP id 4CW8yr5jPjz75Xh; Wed, 11 Nov 2020 11:16:36 +0800 (CST) Received: from [127.0.0.1] (10.74.149.191) by DGGEMS404-HUB.china.huawei.com (10.3.19.204) with Microsoft SMTP Server id 14.3.487.0; Wed, 11 Nov 2020 11:16:37 +0800 Subject: Re: [PATCH V2 net-next 11/11] net: hns3: add debugfs support for interrupt coalesce To: Jakub Kicinski CC: , , , , , References: <1604892159-19990-1-git-send-email-tanhuazhong@huawei.com> <1604892159-19990-12-git-send-email-tanhuazhong@huawei.com> <20201110172858.5eddc276@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> From: tanhuazhong Message-ID: Date: Wed, 11 Nov 2020 11:16:37 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20201110172858.5eddc276@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.74.149.191] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/11/11 9:28, Jakub Kicinski wrote: > On Mon, 9 Nov 2020 11:22:39 +0800 Huazhong Tan wrote: >> Since user may need to check the current configuration of the >> interrupt coalesce, so add debugfs support for query this info, >> which includes DIM profile, coalesce configuration of both software >> and hardware. >> >> Signed-off-by: Huazhong Tan > > Please create a file per vector so that users can just read it instead > of dumping the info into the logs. > This patch should be removed from this series right now. Since this new read method needs some adaptations and verifications, and there maybe another better ways to dump this info. > Even better we should put as much of this information as possible into > the ethtool API. dim state is hardly hardware-specific. > Should the ethtool API used to dump the hardware info? Could you provide some hints to do it? > . >