From: Nidhia Varghese <nidhiavarghese93@gmail.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] Working of pipeline in a given config file and regarding user-defined actions in IP_PIPELINE application
Date: Tue, 11 Apr 2017 13:18:50 +0530 [thread overview]
Message-ID: <CAAx9ALUXSh6M6vFB-WT5Vh-4VpaA7F=GdYjkJEMyfojkNY4ppw@mail.gmail.com> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891265278A197@IRSMSX108.ger.corp.intel.com>
Hi Cristian,
Thanks for your help.
If that is the case, is there any way to use the incoming port as a key for
table lookup? I need to use incoming port along with some other fields of
each packet as the key for my application.
On Mon, Apr 10, 2017 at 3:09 PM, Dumitrescu, Cristian <
cristian.dumitrescu@intel.com> wrote:
> Hi Nidhia,
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nidhia Varghese
> > Sent: Monday, April 10, 2017 8:27 AM
> > To: Singh, Jasvinder <jasvinder.singh@intel.com>
> > Cc: dev@dpdk.org; users@dpdk.org
> > Subject: Re: [dpdk-dev] Working of pipeline in a given config file and
> > regarding user-defined actions in IP_PIPELINE application
> >
> > Hi Jasvinder,
> >
> > Thanks for your help.
> >
> > What I understood from the programmer's guide is that, port action
> handler
> > can be assigned to each input/output port to define actions to be
> executed
> > on each input packet that is received by the port. But one pipeline can
> > have more than one input and output ports. Actions that has to be done to
> > packets coming from each port can be different even though it is in the
> > same pipeline.
>
> Yes, this is correct, the librte_pipeline allows you to configure
> independent action handlers for each input port/output port/table in the
> pipeline.
>
> How can we define different actions for different ports in
> > this case where we have more than one ports for reception or transmission
> > in same pipeline? Which parameter is used to distinguish the ports?
>
> However, in the ip_pipeline application so far, only the pass-through
> pipeline provide an example of an input port action handler, and the same
> AH is set up for all input ports. If you want different AH for different
> ports, you probably need to implement your own AH functions and add some
> pipeline type specific parameters to the configuration file syntax in order
> to assign different actions to different ports.
>
> >
> > Thanks,
> > Nidhia
> >
>
> Regards,
> Cristian
>
>
--
Regards,
Nidhia Varghese
next prev parent reply other threads:[~2017-04-11 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 9:06 [dpdk-users] " Nidhia Varghese
2017-04-07 11:20 ` [dpdk-users] [dpdk-dev] " Singh, Jasvinder
2017-04-10 7:27 ` Nidhia Varghese
2017-04-10 9:27 ` Singh, Jasvinder
2017-04-10 9:39 ` Dumitrescu, Cristian
2017-04-11 7:48 ` Nidhia Varghese [this message]
2017-04-11 9:04 ` Dumitrescu, Cristian
2017-04-18 5:40 ` Nidhia Varghese
2017-04-18 9:53 ` Dumitrescu, Cristian
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='CAAx9ALUXSh6M6vFB-WT5Vh-4VpaA7F=GdYjkJEMyfojkNY4ppw@mail.gmail.com' \
--to=nidhiavarghese93@gmail.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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).