From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f177.google.com (mail-wr0-f177.google.com [209.85.128.177]) by dpdk.org (Postfix) with ESMTP id 4B179282; Tue, 11 Apr 2017 09:48:51 +0200 (CEST) Received: by mail-wr0-f177.google.com with SMTP id z109so23111164wrb.1; Tue, 11 Apr 2017 00:48:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hgEungWnOgvdJ9QbTjX6aKlDBESfWyGIxWU+KqWEVQo=; b=k4lfEsU4ZBdydyk14WTnupY1MIaFYZ85Krdfvyh9SqtfWwrEpm2ekfx483RAr0gUJk +dTQEMuPFnpE6STE4OI1PDt5QFqfpDdffK7zK08XEhDZb6lLZoleUfV0g4ohhV/0ub2J AeMYJwwTipGoloxcTlAOUVinm5+2xF4qDimyfYLUtdKZRIak9Y4ShThvaGwWHpC7lkLl MbOmCFuhjD1dZX+qFiUnGZFl2ZZUJoEAaBgnA/6u9rejmEh5CDnObfyHq09iIr3L90pR Cn2OUQ53wHgWUbQ5ZtmXC6Xa59x8Gt8o02vgfWN15Z4MUCxF3aszMq3cZrw+mIIj9vPk tEqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hgEungWnOgvdJ9QbTjX6aKlDBESfWyGIxWU+KqWEVQo=; b=fsCPRtU5W0+g7JrgrCgWCJlAgsVgInEzxV9V2SLtkii4agZ1Uakw1oc2Yo3beF6vxN KDT/jq7RS/fyenFJ9DABAYsQJY0mcp4cPmb2AMyW43u8qD6/bKFq0dI/DSNdk5kfR8zL e2EYgjgPmzcHjyhDtu+CC+DdFFKYHwjwj8iF16wdUgmuQCn7OCwphiKKj7FZqThKh93p O7wGlFyBANeplFGOJ6wWohlW5VExbh6ptXF27Kx7ReDS9qrO/kUKuSj8Jbck4r9x4YeF 11CWAjNLoWcz3ZCkJcMH3QP8eLzUTWD3V3u0pAwRALIp+83ubMbtmcdS2OGY5Zcxazyc wKMg== X-Gm-Message-State: AN3rC/7KZ51TpU0bz8wDFr67ehqj/L8mhzHC4R4DHWb8QCeyaCeWu6tonJwq540+nPZBu4ZhqukjHQm0Uio5dQ== X-Received: by 10.223.176.133 with SMTP id i5mr20333112wra.53.1491896930793; Tue, 11 Apr 2017 00:48:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.169.68 with HTTP; Tue, 11 Apr 2017 00:48:50 -0700 (PDT) In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891265278A197@IRSMSX108.ger.corp.intel.com> References: <54CBAA185211B4429112C315DA58FF6D31B4B2B1@IRSMSX103.ger.corp.intel.com> <3EB4FA525960D640B5BDFFD6A3D891265278A197@IRSMSX108.ger.corp.intel.com> From: Nidhia Varghese Date: Tue, 11 Apr 2017 13:18:50 +0530 Message-ID: To: "Dumitrescu, Cristian" Cc: "Singh, Jasvinder" , "dev@dpdk.org" , "users@dpdk.org" Content-Type: text/plain; charset=UTF-8 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 07:48:51 -0000 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 > > 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