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 0CF2241E96; Wed, 15 Mar 2023 03:02:34 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8817240A7A; Wed, 15 Mar 2023 03:02:33 +0100 (CET) Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189]) by mails.dpdk.org (Postfix) with ESMTP id 95721400EF for ; Wed, 15 Mar 2023 03:02:31 +0100 (CET) Received: from dggpeml500024.china.huawei.com (unknown [172.30.72.57]) by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4Pbttt2rJGzKmvD; Wed, 15 Mar 2023 10:02:14 +0800 (CST) Received: from [10.67.100.224] (10.67.100.224) by dggpeml500024.china.huawei.com (7.185.36.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Wed, 15 Mar 2023 10:02:28 +0800 Subject: Re: [PATCH] app/testpmd: support dump ethdev private cmd To: Ferruh Yigit , , Aman Singh , Yuying Zhang CC: References: <20230314115035.33356-1-fengchengwen@huawei.com> From: fengchengwen Message-ID: Date: Wed, 15 Mar 2023 10:02:28 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.100.224] X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To dggpeml500024.china.huawei.com (7.185.36.10) 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/3/14 21:45, Ferruh Yigit wrote: > On 3/14/2023 11:50 AM, Chengwen Feng wrote: >> This patch adds 'dump_eth_priv [port_id]' which could used to dump >> the specific ethdev port private info. >> > > We have already "show port ..." commands to display various port related > information, what do you think to follow same syntax for port private info. > > Something like "show port private_info " > > > Or it is possible to append this to the output of the existing port info > ("show port info "), > as a new section of output if port has private info? > > This can be an addition parameter to existing command but not sure if we > need it, like: > "show port info private on" > > I think displaying private info as port of port info without additional > parameter is OK, it is simpler. +1 for this, will send a new patch. Thanks. > > ...