From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jasvinder.singh@intel.com>
Received: from mga07.intel.com (mga07.intel.com [134.134.136.100])
 by dpdk.org (Postfix) with ESMTP id 7EC382BB0
 for <users@dpdk.org>; Mon, 10 Apr 2017 11:27:09 +0200 (CEST)
Received: from orsmga003.jf.intel.com ([10.7.209.27])
 by orsmga105.jf.intel.com with ESMTP; 10 Apr 2017 02:27:07 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.37,181,1488873600"; 
 d="scan'208,217";a="954201514"
Received: from jasvinde-mobl.ger.corp.intel.com (HELO [10.237.221.60])
 ([10.237.221.60])
 by orsmga003.jf.intel.com with ESMTP; 10 Apr 2017 02:27:02 -0700
To: Nidhia Varghese <nidhiavarghese93@gmail.com>
References: <CAAx9ALXyBcBAKr+73nL252KhK-W4VhLn_7ADpiZJXxX_FTQwuw@mail.gmail.com>
 <54CBAA185211B4429112C315DA58FF6D31B4B2B1@IRSMSX103.ger.corp.intel.com>
 <CAAx9ALXEykK+gSy=ytjwSMDg83XftmtaD5wJmUy99bM3DaqYeg@mail.gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
Message-ID: <58EB4FE5.7070309@intel.com>
Date: Mon, 10 Apr 2017 10:27:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <CAAx9ALXEykK+gSy=ytjwSMDg83XftmtaD5wJmUy99bM3DaqYeg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dpdk-users] [dpdk-dev] Working of pipeline in a given config
 file and regarding user-defined actions in IP_PIPELINE application
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 09:27:10 -0000

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.