From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9807142D06; Tue, 20 Jun 2023 10:14:33 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 64E3F4068E; Tue, 20 Jun 2023 10:14:33 +0200 (CEST) Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by mails.dpdk.org (Postfix) with ESMTP id 1823E400D6 for ; Tue, 20 Jun 2023 10:14:32 +0200 (CEST) Received: from kwepemi500020.china.huawei.com (unknown [172.30.72.53]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4QlfXr3sdzzTlQW; Tue, 20 Jun 2023 16:13:48 +0800 (CST) Received: from [10.67.103.42] (10.67.103.42) by kwepemi500020.china.huawei.com (7.221.188.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Tue, 20 Jun 2023 16:14:28 +0800 Message-ID: Date: Tue, 20 Jun 2023 16:14:27 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [PATCH v4 3/3] ring: add telemetry cmd for ring info To: David Marchand CC: , , , , , Thomas Monjalon References: <20230131022841.10775-1-haijie1@huawei.com> <20230210024835.33804-1-haijie1@huawei.com> <20230210024835.33804-4-haijie1@huawei.com> From: Jie Hai In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.103.42] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To kwepemi500020.china.huawei.com (7.221.188.8) X-CFilter-Loop: Reflected X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On 2023/2/20 20:55, David Marchand wrote: > On Fri, Feb 10, 2023 at 3:50 AM Jie Hai wrote: >> >> This patch supports dump of ring information by its name. >> An example using this command is shown below: >> >> --> /ring/info,MP_mb_pool_0 >> { >> "/ring/info": { >> "name": "MP_mb_pool_0", >> "socket": 0, >> "flags": "0x0", >> "producer_type": "MP", >> "consumer_type": "MC", >> "size": 262144, >> "mask": "0x3ffff", >> "capacity": 262143, >> "used_count": 153197, >> "consumer_tail": 2259, >> "consumer_head": 2259, >> "producer_tail": 155456, >> "producer_head": 155456, > > What would an external user make of such an information? > > I'd like to have a better idea what your usecase is. > If it is for debugging, well, gdb is probably a better candidate. > > Hi David, Thanks for your question and I'm sorry for getting back to you so late. There was a problem with my mailbox and I lost all my mails. The ring information exported by telemetry can be used to check the ring status periodically during normal use. When an error occurs, the fault cause can be deduced based on the information. GDB is more suitable for locating errors only when they are sure that errors will occur. >> "mz_name": "RG_MP_mb_pool_0", >> "mz_len": 2097536, >> "mz_hugepage_sz": 1073741824, >> "mz_socket_id": 0, >> "mz_flags": "0x0" >> } >> } > >