[dpdk-dev] Working of pipeline in a given config file and regarding user-defined actions in IP_PIPELINE application
cristian.dumitrescu at intel.com
Mon Apr 10 11:39:51 CEST 2017
> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Nidhia Varghese
> Sent: Monday, April 10, 2017 8:27 AM
> To: Singh, Jasvinder <jasvinder.singh at intel.com>
> Cc: dev at dpdk.org; users at 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.
More information about the dev