DPDK usage discussions
 help / color / mirror / Atom feed
From: longtb5@viettel.com.vn
To: <users@dpdk.org>
Cc: <cristian.dumitrescu@intel.com>
Subject: [dpdk-users] IP PIPELINE tap device
Date: Mon, 30 Oct 2017 18:09:25 +0700 (ICT)	[thread overview]
Message-ID: <001701d3516f$b8b02e50$2a108af0$@viettel.com.vn> (raw)

Hi,
I'm writing a new pipeline type called pipeline_tap, which has one input and
two outputs. The outputs are simply duplications of the input, so basically
like a l2fwd but with two outputs. There has already been great suggestions
[1] on the mailing list to use the l2fwd sample app as a starting point, but
I want to implement this using IP pipeline/packet framework as I would like
to use this device in my IP pipeline application.

As I understand here's what I must provide in order to make my pipeline_tap:
an input port, at least one table, and two output ports.

I have a couple of questions:
First, according to the doc [2], my input port can only be connected to one
table. Moreover, a packet coming from my input port can only hit one table
entry. However it's not clear whether that one table entry can be connected
to TWO output ports. 
Second, I'm having trouble understanding the implementation for table user
actions and table reserved actions in rte_pipeline_run() [3], with all the
mask thingy. Any pointers would be highly appreciated!

Regards,
BL

[1] http://dpdk.org/ml/archives/dev/2015-July/021293.html
[2]
http://dpdk.org/doc/guides/prog_guide/packet_framework.html#connectivity-of-
ports-and-tables
[3]
http://dpdk.org/browse/dpdk/tree/lib/librte_pipeline/rte_pipeline.c?h=v17.11
-rc2#n1344

             reply	other threads:[~2017-10-30 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 11:09 longtb5 [this message]
2017-11-01 18:11 ` Dumitrescu, Cristian
2017-11-02  3:47   ` longtb5

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='001701d3516f$b8b02e50$2a108af0$@viettel.com.vn' \
    --to=longtb5@viettel.com.vn \
    --cc=cristian.dumitrescu@intel.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).