DPDK patches and discussions
 help / color / mirror / Atom feed
From: longtb5@viettel.com.vn
To: marko.kovacevic@intel.com
Cc: dev@dpdk.org, longtb5 <longtb5@viettel.com.vn>
Subject: [dpdk-dev] [PATCH v2] doc: update ip pipeline callback functions
Date: Thu,  8 Feb 2018 08:19:03 +0700 (ICT)	[thread overview]
Message-ID: <1518052913-4862-1-git-send-email-longtb5@viettel.com.vn> (raw)
In-Reply-To: <1517488514-70456-1-git-send-email-longtb5@viettel.com.vn>

From: longtb5 <longtb5@viettel.com.vn>

Update f_post_init for pipeline frontend.
Move f_track from pipeline backend to pipeline frontend.

Signed-off-by: Bao-Long Tran <longtb5@viettel.com.vn>
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
---
 doc/guides/sample_app_ug/ip_pipeline.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst
index e0aa148..dd0a23f 100644
--- a/doc/guides/sample_app_ug/ip_pipeline.rst
+++ b/doc/guides/sample_app_ug/ip_pipeline.rst
@@ -876,8 +876,6 @@ The front-end communicates with the back-end through message queues.
    |            |                  | of some requests which are mandatory for all pipelines (e.g.       |
    |            |                  | ping, statistics).                                                 |
    +------------+------------------+--------------------------------------------------------------------+
-   | f_track    | Function pointer | See section Tracking pipeline output port to physical link         |
-   +------------+------------------+--------------------------------------------------------------------+
 
 
 .. _table_ip_pipelines_front_end:
@@ -892,6 +890,10 @@ The front-end communicates with the back-end through message queues.
    | f_init     | Function pointer      | Function to initialize the front-end of the current pipeline      |
    |            |                       | instance.                                                         |
    +------------+-----------------------+-------------------------------------------------------------------+
+   | f_post_init| Function pointer      | Function to run once after f_init.                                |
+   +------------+-----------------------+-------------------------------------------------------------------+
+   | f_track    | Function pointer      | See section Tracking pipeline output port to physical link.       |
+   +------------+-----------------------+-------------------------------------------------------------------+
    | f_free     | Function pointer      | Function to free the resources allocated by the front-end of      |
    |            |                       | the current pipeline instance.                                    |
    +------------+-----------------------+-------------------------------------------------------------------+
-- 
2.7.4

  parent reply	other threads:[~2018-02-08  1:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 12:32 [dpdk-dev] [PATCH] doc/ip_pipeline.rst: update f_post_init and correct f_track longtb5
2018-02-07 13:55 ` Kovacevic, Marko
2018-02-08  1:19 ` longtb5 [this message]
2018-02-08 21:55   ` [dpdk-dev] [PATCH v2] doc: update ip pipeline callback functions 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=1518052913-4862-1-git-send-email-longtb5@viettel.com.vn \
    --to=longtb5@viettel.com.vn \
    --cc=dev@dpdk.org \
    --cc=marko.kovacevic@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).