DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mauricio Vasquez B <mauricio.vasquezbernal@studenti.polito.it>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 03/19] doc: fix exception path sample app hard-coded references
Date: Thu, 25 Feb 2016 18:02:29 +0100	[thread overview]
Message-ID: <1456419765-8566-4-git-send-email-mauricio.vasquezbernal@studenti.polito.it> (raw)
In-Reply-To: <1456419765-8566-1-git-send-email-mauricio.vasquezbernal@studenti.polito.it>

Signed-off-by: Mauricio Vasquez B <mauricio.vasquezbernal@studenti.polito.it>
---
 doc/guides/sample_app_ug/exception_path.rst          | 5 ++---
 doc/guides/sample_app_ug/l2_forward_real_virtual.rst | 4 ++++
 2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/doc/guides/sample_app_ug/exception_path.rst b/doc/guides/sample_app_ug/exception_path.rst
index c3f8f88..161b6e0 100644
--- a/doc/guides/sample_app_ug/exception_path.rst
+++ b/doc/guides/sample_app_ug/exception_path.rst
@@ -134,8 +134,7 @@ The following sections provide some explanation of the code.
 Initialization
 ~~~~~~~~~~~~~~
 
-Setup of the mbuf pool, driver and queues is similar to the setup done in the L2 Forwarding sample application
-(see Chapter 9 "L2 forwarding Sample Application (in Real and Virtualized Environments" for details).
+Setup of the mbuf pool, driver and queues is similar to the setup done in the :ref:`l2_fwd_app_real_and_virtual`.
 In addition, the TAP interfaces must also be created.
 A TAP interface is created for each lcore that is being used.
 The code for creating the TAP interface is as follows:
@@ -221,7 +220,7 @@ This function first checks the lcore_id against the user provided input_cores_ma
 if this core is reading from or writing to a TAP interface.
 
 For the case that reads from a NIC port, the packet reception is the same as in the L2 Forwarding sample application
-(see Section 9.4.6, "Receive, Process and Transmit Packets").
+(see :ref:`l2_fwd_app_rx_tx_packets`).
 The packet transmission is done by calling write() with the file descriptor of the appropriate TAP interface
 and then explicitly freeing the mbuf back to the pool.
 
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 6e61b4b..12f0d27 100644
--- a/doc/guides/sample_app_ug/l2_forward_real_virtual.rst
+++ b/doc/guides/sample_app_ug/l2_forward_real_virtual.rst
@@ -28,6 +28,8 @@
     (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
     OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
+.. _l2_fwd_app_real_and_virtual:
+
 L2 Forwarding Sample Application (in Real and Virtualized Environments)
 =======================================================================
 
@@ -387,6 +389,8 @@ The global configuration for TX queues is stored in a static structure:
         .tx_free_thresh = RTE_TEST_TX_DESC_DEFAULT + 1, /* disable feature */
     };
 
+.. _l2_fwd_app_rx_tx_packets:
+
 Receive, Process and Transmit Packets
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- 
1.9.1

  parent reply	other threads:[~2016-02-25 17:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 17:02 [dpdk-dev] [PATCH 00/19] fix hard-coded references in sample apps guide Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 01/19] doc: fix vhost sample app hard-coded references Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 02/19] doc: fix distributor sample application " Mauricio Vasquez B
2016-02-25 17:02 ` Mauricio Vasquez B [this message]
2016-02-25 17:02 ` [dpdk-dev] [PATCH 04/19] doc: fix intel quickAssist technology sample app " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 05/19] doc: fix ip fragmentation " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 06/19] doc: fix ip reassembly " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 07/19] doc: fix multicast " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 08/19] doc: fix kepp alive " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 09/19] doc: fix kni " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 10/19] doc: fix l2 fwd " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 11/19] doc: fix l3 " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 12/19] doc: fix l3fwd access control " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 13/19] doc: fix l3fwd power man " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 14/19] doc: fix l3fwd virtual " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 15/19] doc: fix link status int " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 16/19] doc: fix multi-process " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 17/19] doc: fix tep termination " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 18/19] doc: fix vmdq and dcb fwd " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 19/19] doc: fix vm power man " Mauricio Vasquez B
2016-03-07 20:42 ` [dpdk-dev] [PATCH 00/19] fix hard-coded references in sample apps guide 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=1456419765-8566-4-git-send-email-mauricio.vasquezbernal@studenti.polito.it \
    --to=mauricio.vasquezbernal@studenti.polito.it \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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).