From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ferruh Yigit <ferruh.yigit@intel.com>, Xiaoyun Li <xiaoyun.li@intel.com>
Cc: dev@dpdk.org, Xueming Li <xuemingl@nvidia.com>,
Viacheslav Galaktionov <viacheslav.galaktionov@oktetlabs.ru>,
Andy Moreton <amoreton@xilinx.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: add command to print representor info
Date: Wed, 15 Sep 2021 16:50:14 +0300 [thread overview]
Message-ID: <4cadb202-d4da-7b86-01a1-c4e117e3cbd8@oktetlabs.ru> (raw)
In-Reply-To: <7591e9b6-feea-e7e9-ff07-3c35d1243031@intel.com>
On 9/14/21 7:36 PM, Ferruh Yigit wrote:
> On 9/14/2021 5:17 PM, Andrew Rybchenko wrote:
>> On 9/14/21 6:52 PM, Ferruh Yigit wrote:
>>> On 8/31/2021 5:12 PM, Andrew Rybchenko wrote:
>>>> From: Viacheslav Galaktionov <viacheslav.galaktionov@oktetlabs.ru>
>>>>
>>>> Make it simpler to debug configurations and code related to the representor
>>>> info API.
>>>>
>>>> Signed-off-by: Viacheslav Galaktionov <viacheslav.galaktionov@oktetlabs.ru>
>>>> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>>>> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
>>>> ---
>>>> v2:
>>>> - change output format to log just one line per range
>>>>
>>>> app/test-pmd/cmdline.c | 135 +++++++++++++++++++++++++++++++++++++++++
>>>> 1 file changed, 135 insertions(+)
>>>>
>>>> diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c
>>>> index 82253bc751..ae700f9dd1 100644
>>>> --- a/app/test-pmd/cmdline.c
>>>> +++ b/app/test-pmd/cmdline.c
>>>> @@ -236,6 +236,10 @@ static void cmd_help_long_parsed(void *parsed_result,
>>>> " Show port supported ptypes"
>>>> " for a specific port\n\n"
>>>>
>>>> + "show port (port_id) representor info\n"
>>>> + " Show supported representors"
>>>> + " for a specific port\n\n"
>>>> +
>>>
>>> What do you think extending existing "show port info #" command instead of
>>> creating a new command for it?
>>
>> My fear with such approach is that output of the "show port
>> info #" is already too long and adding representors info
>> there will make it even much longer.
>>
>
> That is fair concern, what about extend existing command with a new keyword to
> just print representor info:
> "show port info # representor"
Good idea, see v3.
>>> Since "show port info #" is a well known command, it can simplify the usage.
>>> When port is representor port it can display additional info.
>>>
>>
>> Just to be clear: it will output information for "backer"
>> (or parent) port which should be used to create representors.
>>
next prev parent reply other threads:[~2021-09-15 13:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 6:39 [dpdk-dev] [PATCH] " Andrew Rybchenko
2021-08-27 7:28 ` Li, Xiaoyun
2021-08-27 8:20 ` Xueming(Steven) Li
2021-08-27 9:20 ` Viacheslav Galaktionov
2021-08-28 13:28 ` Xueming(Steven) Li
2021-08-31 16:12 ` [dpdk-dev] [PATCH v2] " Andrew Rybchenko
2021-09-02 12:33 ` Xueming(Steven) Li
2021-09-14 15:52 ` Ferruh Yigit
2021-09-14 16:17 ` Andrew Rybchenko
2021-09-14 16:36 ` Ferruh Yigit
2021-09-15 13:50 ` Andrew Rybchenko [this message]
2021-09-15 13:47 ` [dpdk-dev] [PATCH v3] " Andrew Rybchenko
2021-09-28 0:55 ` Ajit Khaparde
2021-10-11 8:32 ` Li, Xiaoyun
2021-10-11 13:10 ` Andrew Rybchenko
2021-10-11 13:08 ` [dpdk-dev] [PATCH v4] " Andrew Rybchenko
2021-10-12 1:50 ` Li, Xiaoyun
2021-10-12 17:06 ` Ferruh Yigit
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=4cadb202-d4da-7b86-01a1-c4e117e3cbd8@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=amoreton@xilinx.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=viacheslav.galaktionov@oktetlabs.ru \
--cc=xiaoyun.li@intel.com \
--cc=xuemingl@nvidia.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).