From: longtb5@viettel.com.vn
To: bruce.richardson@intel.com
Cc: dev@dpdk.org, Bao-Long Tran <longtb5@viettel.com.vn>, stable@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2] doc: remove old Rx/Tx configuration info in l2fwd
Date: Mon, 3 Jun 2019 17:06:23 +0700 (ICT) [thread overview]
Message-ID: <1559557107-115815-3-git-send-email-longtb5@viettel.com.vn> (raw)
In-Reply-To: <1559557107-115815-1-git-send-email-longtb5@viettel.com.vn>
Update doc the match with code.
Fixes: 81f7ecd9 ("examples: use factorized default Rx/Tx configuration")
Cc: stable@dpdk.org
Signed-off-by: Bao-Long Tran <longtb5@viettel.com.vn>
---
doc/guides/sample_app_ug/l2_forward_real_virtual.rst | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/doc/guides/sample_app_ug/l2_forward_real_virtual.rst b/doc/guides/sample_app_ug/l2_forward_real_virtual.rst
index bede06e..39d6b00 100644
--- a/doc/guides/sample_app_ug/l2_forward_real_virtual.rst
+++ b/doc/guides/sample_app_ug/l2_forward_real_virtual.rst
@@ -281,18 +281,6 @@ The list of queues that must be polled for a given lcore is stored in a private
The values n_rx_port and rx_port_list[] are used in the main packet processing loop
(see :ref:`l2_fwd_app_rx_tx_packets`).
-The global configuration for the RX queues is stored in a static structure:
-
-.. code-block:: c
-
- static const struct rte_eth_rxconf rx_conf = {
- .rx_thresh = {
- .pthresh = RX_PTHRESH,
- .hthresh = RX_HTHRESH,
- .wthresh = RX_WTHRESH,
- },
- };
-
.. _l2_fwd_app_tx_init:
TX Queue Initialization
--
2.7.4
next prev parent reply other threads:[~2019-06-03 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 10:06 [dpdk-dev] [PATCH 0/2] clean up old Rx/Tx configuration leftovers longtb5
2019-06-03 10:06 ` [dpdk-dev] [PATCH 1/2] examples/l3fwd-vf: remove old Rx/Tx configuration defines longtb5
2019-06-03 10:06 ` longtb5 [this message]
2019-07-01 19:50 ` [dpdk-dev] [PATCH 0/2] clean up old Rx/Tx configuration leftovers Thomas Monjalon
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=1559557107-115815-3-git-send-email-longtb5@viettel.com.vn \
--to=longtb5@viettel.com.vn \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).