From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
"Sun, Chenmin" <chenmin.sun@intel.com>
Cc: "Wang, Haiyue" <haiyue.wang@intel.com>
Subject: Re: [dpdk-dev] [RFC v3 4/4] app/testpmd: show the Rx/Tx burst mode description
Date: Thu, 12 Sep 2019 16:07:59 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260DF7419@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20190910163337.4843-5-haiyue.wang@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Haiyue Wang
> Sent: Tuesday, September 10, 2019 5:34 PM
> To: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; mdr@ashroe.eu; Sun,
> Chenmin <chenmin.sun@intel.com>
> Cc: Wang, Haiyue <haiyue.wang@intel.com>
> Subject: [dpdk-dev] [RFC v3 4/4] app/testpmd: show the Rx/Tx burst mode
> description
>
> Add the 'Burst mode' section into command 'show rxq|txq info <port_id>
> <queue_id>' to show the Rx/Tx burst mode description like:
> "Burst mode: Vector AVX2 Scattered"
>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
next prev parent reply other threads:[~2019-09-12 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 16:33 [dpdk-dev] [RFC v3 0/4] get Rx/Tx packet burst mode information Haiyue Wang
2019-09-10 16:33 ` [dpdk-dev] [RFC v3 1/4] ethdev: add the API for getting " Haiyue Wang
2019-09-10 16:33 ` [dpdk-dev] [RFC v3 2/4] net/i40e: support to get the Rx/Tx burst mode Haiyue Wang
2019-09-10 16:33 ` [dpdk-dev] [RFC v3 3/4] net/ice: " Haiyue Wang
2019-09-10 16:33 ` [dpdk-dev] [RFC v3 4/4] app/testpmd: show the Rx/Tx burst mode description Haiyue Wang
2019-09-12 16:07 ` Iremonger, Bernard [this message]
2019-09-25 16:33 ` Wang, Haiyue
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=8CEF83825BEC744B83065625E567D7C260DF7419@IRSMSX108.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=chenmin.sun@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.com \
--cc=mdr@ashroe.eu \
/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).