From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH v4] librte_pipeline: add support for packet
	redirection at action handlers
Date: Mon, 07 Mar 2016 12:01:51 +0100
Message-ID: <13895624.4YkCxv7Jex@xps13>
References: <1456951307-35264-1-git-send-email-jasvinder.singh@intel.com>
 <1457002906-69859-1-git-send-email-jasvinder.singh@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: Jasvinder Singh <jasvinder.singh@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44])
 by dpdk.org (Postfix) with ESMTP id B31162C62
 for <dev@dpdk.org>; Mon,  7 Mar 2016 12:03:28 +0100 (CET)
Received: by mail-wm0-f44.google.com with SMTP id l68so80292834wml.0
 for <dev@dpdk.org>; Mon, 07 Mar 2016 03:03:28 -0800 (PST)
In-Reply-To: <1457002906-69859-1-git-send-email-jasvinder.singh@intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi Jasvinder,

Don't hesitate to leave some blank lines in your message, it's free :)

2016-03-03 11:01, Jasvinder Singh:
> Currently, there is no mechanism that allows the pipeline ports (in/out) and
> table action handlers to override the default forwarding decision (as
> previously configured per input port or in the table entry). Therefore, new
> pipeline API functions have been added which allows action handlers to
> hijack packets and remove them from the pipeline processing, and then either
> drop them or send them out of the pipeline on any output port. The port
> (in/out) and table action handler prototypes have been changed for making
> use of these new API functions. This feature will be helpful to implement
> functions such as exception handling (e.g. TTL =0), load balancing etc.
> Changes are made to the ports and table action handlers defined in
> app/test_pipeline and ip_pipeline sample application.

I have the feeling it would be easier to parse if the structure changes were
done in a separate commit, then introduce the new function.

You have forgotten to remove the deprecation notice.