DPDK usage discussions
 help / color / mirror / Atom feed
From: Gadre Nayan <gadrenayan@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Tracking pipeline ports.
Date: Mon, 18 Jul 2016 21:12:21 +0530	[thread overview]
Message-ID: <CAKJ7aR5dL83E+jJHGY_2wZteYO_cL=jfN6v7Lid6A275L=8j8g@mail.gmail.com> (raw)

Hi,

I wanted to understand the purpose of the f_track function.

In the IP_pipeline example there are 2 instances where the f_track is used.

1. pipeline_firewall:
static int pipeline_firewall_track(void *pipeline, __rte_unused
uint32_t port_in,
        uint32_t *port_out)
{
        struct pipeline *p = (struct pipeline *) pipeline;

        /* Check input arguments */
        if ((p == NULL) ||
                (port_in >= p->n_ports_in) ||
                (port_out == NULL))
                return -1;

        if (p->n_ports_in == 1) {
                *port_out = 0;
                return 0;
        }

        return -1;
}

2. Passthrough:

static int
pipeline_passthrough_track(void *pipeline, uint32_t port_in, uint32_t *port_out)
{
        struct pipeline *p = (struct pipeline *) pipeline;

        /* Check input arguments */
        if ((p == NULL) ||
                (port_in >= p->n_ports_in) ||
                (port_out == NULL))
                return -1;

        *port_out = port_in / p->n_ports_in;
        return 0;
}

1. What is a actual use of this function ?
Quoting the documentation:
"In some cases, it is useful for a pipeline instance to get
application level information related to pipeline connectivity, such
as to identify the output link (e.g. physical NIC port) where one of
its output ports connected, either directly or indirectly by
traversing other pipeline instances."

2. The 1st condition check remains same in both. But in pass-through
port_out is assigned some value. what does this mean ?

             reply	other threads:[~2016-07-18 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 15:42 Gadre Nayan [this message]
2016-07-18 17:09 ` Singh, Jasvinder

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='CAKJ7aR5dL83E+jJHGY_2wZteYO_cL=jfN6v7Lid6A275L=8j8g@mail.gmail.com' \
    --to=gadrenayan@gmail.com \
    --cc=users@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).