From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: display devargs in port info output
Date: Thu, 11 Oct 2018 12:00:44 +0100 [thread overview]
Message-ID: <436c6163-1cba-066a-346e-fccc1d150c87@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260D10171@IRSMSX107.ger.corp.intel.com>
On 10/10/2018 2:30 PM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: Yigit, Ferruh
>> Sent: Wednesday, October 10, 2018 12:42 PM
>> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
>> <jingjing.wu@intel.com>; Iremonger, Bernard <bernard.iremonger@intel.com>
>> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>
>> Subject: [PATCH] app/testpmd: display devargs in port info output
>>
>> Devargs may affect how device works but currently we don't have a way to
>> observe provided devargs.
>>
>> Add ability to print device argument as part of port info,
>>
>> For example, for "--vdev net_pcap0,iface=lo" output will be
>>
>> "
>> ********************* Infos for port 1 ********************* MAC
>> address: 02:70:63:61:70:00 Device name: net_pcap0 Driver name: net_pcap
>> Devargs: iface=lo
>> ....
>> "
>>
>> or for "-w0000:86:00.1,queue-num-per-vf=8",
>>
>> "
>> ********************* Infos for port 0 ********************* MAC
>> address: 3C:FD:FE:AB:B4:41 Device name: 0000:86:00.1 Driver name: net_i40e
>> Devargs: queue-num-per-vf=8
>> ....
>> "
>>
>> `Devargs` line may not be printed at all if devargs is not provided for that device.
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-10-11 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 11:42 Ferruh Yigit
2018-10-10 13:30 ` Iremonger, Bernard
2018-10-11 11:00 ` Ferruh Yigit [this message]
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=436c6163-1cba-066a-346e-fccc1d150c87@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=wenzhuo.lu@intel.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).