From: Haiyue Wang <haiyue.wang@intel.com>
To: dev@dpdk.org, ferruh.yigit@intel.com, mdr@ashroe.eu,
chenmin.sun@intel.com
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-dev] [RFC v3 0/4] get Rx/Tx packet burst mode information
Date: Wed, 11 Sep 2019 00:33:33 +0800 [thread overview]
Message-ID: <20190910163337.4843-1-haiyue.wang@intel.com> (raw)
v1 -> v2:
Avoid ABI breaking, add a simple trace API to export string type
information.
v2 -> v3:
Use bit fields to present the burst mode setting, and rename the
APIs.
Haiyue Wang (4):
ethdev: add the API for getting burst mode information
net/i40e: support to get the Rx/Tx burst mode
net/ice: support to get the Rx/Tx burst mode
app/testpmd: show the Rx/Tx burst mode description
app/test-pmd/config.c | 25 ++++++++
doc/guides/rel_notes/release_19_11.rst | 8 +++
drivers/net/i40e/i40e_ethdev.c | 2 +
drivers/net/i40e/i40e_ethdev.h | 4 ++
drivers/net/i40e/i40e_rxtx.c | 72 +++++++++++++++++++++
drivers/net/ice/ice_ethdev.c | 2 +
drivers/net/ice/ice_rxtx.c | 54 ++++++++++++++++
drivers/net/ice/ice_rxtx.h | 4 ++
lib/librte_ethdev/rte_ethdev.c | 75 ++++++++++++++++++++++
lib/librte_ethdev/rte_ethdev.h | 82 ++++++++++++++++++++++++
lib/librte_ethdev/rte_ethdev_core.h | 5 ++
lib/librte_ethdev/rte_ethdev_version.map | 5 ++
12 files changed, 338 insertions(+)
--
2.17.1
next reply other threads:[~2019-09-10 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 16:33 Haiyue Wang [this message]
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
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=20190910163337.4843-1-haiyue.wang@intel.com \
--to=haiyue.wang@intel.com \
--cc=chenmin.sun@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).