From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: Chengchang Tang <tangchengchang@huawei.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Tahhan, Maryam" <maryam.tahhan@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/procinfo: add device registers dump
Date: Thu, 10 Jun 2021 16:25:34 +0000 [thread overview]
Message-ID: <BYAPR11MB3366BF8F7C53364A1345B29FFF359@BYAPR11MB3366.namprd11.prod.outlook.com> (raw)
In-Reply-To: <0add2988-b4d1-0773-d075-8d51055d9cc2@huawei.com>
> -----Original Message-----
> From: Chengchang Tang <tangchengchang@huawei.com>
> >> + ret = rte_eth_dev_get_reg_info(i, ®_info);
> >> + if (ret) {
> >> + printf("Error getting device reg info: %d\n", ret);
> >> + continue;
> >> + }
> >> +
> >> + buf_size = reg_info.length * reg_info.width;
> >
> >
> > If it is to get the regs length, you can directly call
> "rte_ethtool_get_regs_len(uint16_t port_id)" API , instead of again writing the
> above logic.
> > And use the returned length in below malloc.
>
> This logic is indeed identical to the logic of the "rte_ethtool_get_regs_len" API
> of Ethtool, but the method of using the "rte_eth_dev_get_reg_info" API is the
> case. All users will have similar code logic when using this API.
>
Oh yes, my bad, I overlooked it. It makes complete sense now.
next prev parent reply other threads:[~2021-06-10 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 13:02 Min Hu (Connor)
2021-05-19 10:16 ` Thomas Monjalon
2021-06-04 15:04 ` Pattan, Reshma
2021-06-05 3:15 ` Chengchang Tang
2021-06-10 16:25 ` Pattan, Reshma [this message]
2021-06-21 2:17 ` [dpdk-dev] [PATCH v2] " Min Hu (Connor)
2021-07-09 21:55 ` Thomas Monjalon
2021-07-17 2:16 ` Min Hu (Connor)
2021-07-17 17:51 ` [dpdk-dev] [PATCH] " Stephen Hemminger
2021-07-19 6:40 ` Chengchang Tang
2021-07-17 17:53 ` Stephen Hemminger
2021-07-19 7:00 ` Chengchang Tang
2021-07-22 10:58 ` [dpdk-dev] [PATCH v3] " Min Hu (Connor)
2021-07-29 14:14 ` Pattan, Reshma
2021-07-30 16:46 ` Thomas Monjalon
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=BYAPR11MB3366BF8F7C53364A1345B29FFF359@BYAPR11MB3366.namprd11.prod.outlook.com \
--to=reshma.pattan@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=maryam.tahhan@intel.com \
--cc=tangchengchang@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).