From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Ray Kinsella <mdr@ashroe.eu>
Cc: dpdk-dev <dev@dpdk.org>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Loftus, Ciara" <ciara.loftus@intel.com>,
"Ciara Power" <ciara.power@intel.com>
Subject: Re: [RFC v3] ethdev: introduce ethdev dump API
Date: Thu, 3 Feb 2022 13:21:38 +0000 [thread overview]
Message-ID: <d72d7c05-475b-e701-e960-747395ec2926@intel.com> (raw)
In-Reply-To: <ea1c7931-3bee-4cc9-de40-0bc154b8ac21@huawei.com>
On 1/25/2022 1:45 PM, Min Hu (Connor) wrote:
> Hi, Ferruh,
>
> 在 2022/1/25 20:58, Ferruh Yigit 写道:
>> On 1/25/2022 12:56 PM, Ferruh Yigit wrote:
>>> On 1/18/2022 3:34 PM, Ajit Khaparde wrote:
>>>> On Wed, Jan 12, 2022 at 4:06 AM Ray Kinsella <mdr@ashroe.eu> wrote:
>>>>>
>>>>>
>>>>> Min Hu (Connor) <humin29@huawei.com> writes:
>>>>>
>>>>>> Added the ethdev dump API which provides functions for query private info
>>>>>> from device. There exists many private properties in different PMD drivers,
>>>>>> such as adapter state, Rx/Tx func algorithm in hns3 PMD. The information of
>>>>>> these properties is important for debug. As the information is private,
>>>>>> the new API is introduced.
>>>>>>
>>>>>> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>>>>>> Acked-by: Morten BrÞrup <mb@smartsharesystems.com>
>>>>>> ---
>>>>>> v3:
>>>>>> * fix comment.
>>>>>> * add rte_eth_dev_priv_dump to version.map file.
>>>>>>
>>>>>> v2:
>>>>>> * fix dump API name
>>>>>> * adjust description in doc.
>>>>>> ---
>>>>>> doc/guides/rel_notes/release_22_03.rst | 7 +++++++
>>>>>> lib/ethdev/ethdev_driver.h | 17 +++++++++++++++++
>>>>>> lib/ethdev/rte_ethdev.c | 15 +++++++++++++++
>>>>>> lib/ethdev/rte_ethdev.h | 16 ++++++++++++++++
>>>>>> lib/ethdev/version.map | 3 +++
>>>>>> 5 files changed, 58 insertions(+)
>>>>>>
>>>>>
>>>>> Acked-by: Ray Kinsella <mdr@ashroe.eu>
>>>> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>>>
>>>
>>> I have a concern and this "private info", it can be useful for debug
>>> but still it will lead to a PMD specific applications, I wonder if some
>>> common information can be provided.
> The purpose of introducing the API is to enhance dump ability for NICs.
> It will be used in APP proc-info, I will add "show-port-private" option
> for it. As for common information, I will add them in "show-port" option
> which already exists.
>
Hi Connor,
We briefly touch on this patch in today's release status meeting,
as far as I get general consensus was this can be good for debugging
issues offline (instead of application parsing the output of API).
So can you please send a new, non-RFC, version of the patch?
And please keep the existing ack/review tags.
>
> Is there any list in your mind what
>>> can be part of this private info?
> Private info for NICs, take HNS3 PMD NICS as an example,
> - Dev Capability:
> -- support DCB: no
> -- support COPPER: no
> -- support FD QUEUE REGION: no
> -- support PTP: no
> -- support TX PUSH: no
> -- support INDEP TXRX: no
> -- support STASH: no
> -- support SIMPLE BD: no
> -- support RXD Advanced Layout: no
> -- support OUTER UDP CKSUM: no
> -- support RAS IMP: no
> -- support TM: no
> -- support VF VLAN FILTER MOD: no
> - VLAN Config Info:
> -- Port VLAN filter configuration
> nic_ingress :Disable
> nic_egress :Disable
> -- VF VLAN filter configuration
> nic_ingress :Disable
> nic_egress :Disable
> -- RX VLAN configuration
> vlan1_strip_en :Disable
> vlan2_strip_en :Disable
> vlan1_vlan_prionly :Disable
> vlan2_vlan_prionly :Disable
> vlan1_strip_discard :Disable
> vlan2_strip_discard :Disable
> -- TX VLAN configuration
> accept_tag1 :Enable
> accept_untag1 :Enable
> insert_tag1_en :Disable
> default_vlan_tag1 = 0, qos = 0
> accept_tag2 :Enable
> accept_untag2 :Enable
> insert_tag2_en :Disable
> default_vlan_tag2 = 0, qos = 0
> vlan_shift_mode :Disable
> -- pvid status: off
> - Fdir Info:
> -- mode=0 max_key_len=400 rule_num:512 cnt_num:32
> -- key_sel=1 tuple_active=0x3bdfd890 meta_data_active=0xd0
> -- ipv6_word_en: in_s=3 in_d=3 out_s=0 out_d=0
> ....
>
> These info is private for hns3 PMD.
>
>
>>>
>>> Also why not use existing xstats or telemetry to get more data from the
>>> drivers?
> Xstats is used to query statistics rather than state. Like above info,
> many keys is "enable" or "disable". It is not appropriated to put the
> date in xstats.
>
> Telemetry is used to query common info for NICs, not for private info.
> It is not also appropriated to put private date in telemetry.
>
>
>
>>> As synced with Ciara (cc'ed), she mentioned more information can be get
>>> via registering callbacks to ethdev.
>>
>> Opps, Ciara (Power) cc'ed now.
>> .
next prev parent reply other threads:[~2022-02-03 13:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 11:54 [RFC] ethdev: introduce ethdev dump API Min Hu (Connor)
2022-01-11 12:10 ` Morten Brørup
2022-01-12 2:40 ` Min Hu (Connor)
2022-01-11 12:48 ` Thomas Monjalon
2022-01-12 2:41 ` Min Hu (Connor)
2022-01-12 2:44 ` Min Hu (Connor)
2022-01-12 10:13 ` Thomas Monjalon
2022-01-12 10:56 ` Min Hu (Connor)
2022-01-12 2:40 ` [RFC v2] " Min Hu (Connor)
2022-01-12 7:20 ` Morten Brørup
2022-01-12 11:15 ` Min Hu (Connor)
2022-01-14 17:56 ` Ajit Khaparde
2022-01-15 0:24 ` Min Hu (Connor)
2022-01-18 15:33 ` Ajit Khaparde
2022-01-12 11:14 ` [RFC v3] " Min Hu (Connor)
2022-01-12 12:05 ` Ray Kinsella
2022-01-18 15:34 ` Ajit Khaparde
2022-01-25 12:56 ` Ferruh Yigit
2022-01-25 12:58 ` Ferruh Yigit
2022-01-25 13:45 ` Min Hu (Connor)
2022-02-03 13:21 ` Ferruh Yigit [this message]
2022-02-07 1:37 ` Min Hu (Connor)
2022-02-07 1:35 ` Min Hu (Connor)
2022-02-07 1:47 ` [PATCH] " Min Hu (Connor)
2022-02-07 11:46 ` Ferruh Yigit
2022-02-07 12:18 ` Morten Brørup
2022-02-07 12:35 ` Ferruh Yigit
2022-02-07 12:56 ` Morten Brørup
2022-02-07 15:35 ` Ferruh Yigit
2022-02-08 0:39 ` Min Hu (Connor)
2022-02-08 10:21 ` Ferruh Yigit
2022-02-08 11:14 ` Min Hu (Connor)
2022-02-08 12:59 ` Ferruh Yigit
2022-02-08 13:52 ` Thomas Monjalon
2022-02-09 1:07 ` Min Hu (Connor)
2022-02-09 1:06 ` Min Hu (Connor)
2022-02-08 2:46 ` Min Hu (Connor)
2022-02-08 2:45 ` [PATCH v2] ethdev: introduce " Min Hu (Connor)
2022-02-09 1:21 ` [PATCH v3] " Min Hu (Connor)
2022-02-10 12:32 ` Ferruh Yigit
2022-02-10 12:34 ` Ferruh Yigit
2022-02-11 4:53 ` Min Hu (Connor)
2022-02-10 12:37 ` Ferruh Yigit
2022-02-10 13:16 ` Min Hu (Connor)
2022-02-10 13:22 ` Ferruh Yigit
2022-02-10 15:50 ` Ferruh Yigit
2022-02-11 4:52 ` Min Hu (Connor)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d72d7c05-475b-e701-e960-747395ec2926@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ciara.loftus@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=mb@smartsharesystems.com \
--cc=mdr@ashroe.eu \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.