DPDK usage discussions
 help / color / mirror / Atom feed
From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: Nidhia Varghese <nidhiavarghese93@gmail.com>
Cc: "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: Mon, 10 Apr 2017 10:27:01 +0100	[thread overview]
Message-ID: <58EB4FE5.7070309@intel.com> (raw)
In-Reply-To: <CAAx9ALXEykK+gSy=ytjwSMDg83XftmtaD5wJmUy99bM3DaqYeg@mail.gmail.com>

Hi Nidhia,

On 10/04/2017 08:27, Nidhia Varghese wrote:
> 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. 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?

Although, we haven't done this in the provided code, there is a 
provision to define the action specific to the port.  While initializing 
the pipeline port parameters, specific action can be associated with the 
port. Have a look at pipeline_passthrough_init()  
(pipeline/pipeline_passthrough_be.c) , where during port initialization, 
a specific action can be assigned.

Thanks,
Jasvinder

PS: I have removed "dev@dpdk.org", for such queries we use 
users@dpdk.org mailing list.

  reply	other threads:[~2017-04-10  9:27 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 [this message]
2017-04-10  9:39     ` Dumitrescu, Cristian
2017-04-11  7:48       ` Nidhia Varghese
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=58EB4FE5.7070309@intel.com \
    --to=jasvinder.singh@intel.com \
    --cc=nidhiavarghese93@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).