From: Remy Horton <remy.horton@intel.com>
To: dev@dpdk.org
Cc: John McNamara <john.mcnamara@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH v4 0/4] ethdev: add per-PMD tuning of RxTx parmeters
Date: Fri, 6 Apr 2018 14:54:32 +0100 [thread overview]
Message-ID: <20180406135436.25719-1-remy.horton@intel.com> (raw)
In-Reply-To: Message-ID: <20180404171740.5084-1-remy.horton@intel.com
The optimal values of several transmission & reception related parameters,
such as burst sizes, descriptor ring sizes, and number of queues, varies
between different network interface devices. This patchset allows individual
PMDs to specify their preferred parameter values, and if so indicated by an
application, for them to be used automatically by the ethdev layer.
rte_eth_dev_configure() has been changed so that specifying zero for both
nb_rx_q AND nb_tx_q causes it to use driver preferred values, and if these
are not available, falls back to EAL defaults. Setting one (but not both)
to zero does not cause the use of defaults, as having one of them zeroed is
a valid setup.
This patchset includes per-PMD values for e1000 and i40e but it is expected
that subsequent patchsets will cover other PMDs. A deprecation notice
covering the API/ABI change is in place.
Changes in v4:
* Added API/ABI change documentation
# Rebased to 78f5a2e93d74
Changes in v3:
* Changed formatting around new rte_eth_dev_info fields
* Added Doxygen documentation to struct rte_eth_dev_portconf
* Testpmd "port config all burst 0" and --burst=0 uses PMD
Rx burst recommendations.
* Added to release notes
* Rebased to 8ea081f38161
Changes in v2:
* Rebased to master
* Removed fallback values from rte_eth_dev_info_get()
* Added fallback values to rte_rte_[rt]x_queue_setup()
* Added fallback values to rte_eth_dev_configure()
* Corrected comment
* Removed deprecation notice
* Split RX and Tx into seperate structures
* Changed parameter names
Remy Horton (4):
ethdev: add support for PMD-tuned Tx/Rx parameters
net/e1000: add TxRx tuning parameters
net/i40e: add TxRx tuning parameters
testpmd: make use of per-PMD TxRx parameters
app/test-pmd/cmdline.c | 31 +++++++++++++++++++++---
app/test-pmd/parameters.c | 38 +++++++++++++++++++++++++----
app/test-pmd/testpmd.c | 5 ++--
doc/guides/rel_notes/deprecation.rst | 13 ----------
doc/guides/rel_notes/release_18_05.rst | 35 +++++++++++++++++++++++++++
drivers/net/e1000/em_ethdev.c | 6 +++++
drivers/net/i40e/i40e_ethdev.c | 33 ++++++++++++++++++++++---
lib/librte_ether/rte_ethdev.c | 44 +++++++++++++++++++++++++++-------
lib/librte_ether/rte_ethdev.h | 25 +++++++++++++++++++
9 files changed, 195 insertions(+), 35 deletions(-)
--
2.9.5
next reply other threads:[~2018-04-06 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 13:54 Remy Horton [this message]
2018-04-06 13:54 ` [dpdk-dev] [PATCH v4 1/4] ethdev: add support for PMD-tuned Tx/Rx parameters Remy Horton
2018-04-06 13:54 ` [dpdk-dev] [PATCH v4 2/4] net/e1000: add TxRx tuning parameters Remy Horton
2018-04-06 13:54 ` [dpdk-dev] [PATCH v4 3/4] net/i40e: " Remy Horton
2018-04-06 13:54 ` [dpdk-dev] [PATCH v4 4/4] testpmd: make use of per-PMD TxRx parameters Remy Horton
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=20180406135436.25719-1-remy.horton@intel.com \
--to=remy.horton@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=thomas@monjalon.net \
--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).