From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: Query on Filtering Support in DPDK
Date: Mon, 30 Nov 2015 14:43:18 +0100
Message-ID: <2318875.uXDYP4N6Nj@xps13>
References: <20151130124943.GA15383@scalar.blr.asicdesigners.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, Felix Marti <felix@chelsio.com>,
 Nirranjan Kirubaharan <nirranjan@chelsio.com>,
 Kumar Sanghvi <kumaras@chelsio.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43])
 by dpdk.org (Postfix) with ESMTP id D3AAE2C72
 for <dev@dpdk.org>; Mon, 30 Nov 2015 14:44:27 +0100 (CET)
Received: by wmuu63 with SMTP id u63so130008049wmu.0
 for <dev@dpdk.org>; Mon, 30 Nov 2015 05:44:27 -0800 (PST)
In-Reply-To: <20151130124943.GA15383@scalar.blr.asicdesigners.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,

2015-11-30 18:19, Rahul Lakkireddy:
> 1. Add a new action 'switch' that will:
>    * Allow re-direction to different ports in hardware.
> 
>    Also, for such a rule, additionally support below:
> 
>    * Allow source mac/destination mac and vlan header re-writing to be
>      done by the hardware.
> 
>    * Allow re-write of TCP/IP headers to perform NAT in hardware.
> 
> 2. Add ability to mask individual fields at a particular layer for each
>    filter in flow_director. For example, mask all ip packets coming from
>    a particular subnet mask and particular range of l4 ports for each
>    filter rule.
> 
> We would like to get some suggestions on how to proceed with adding the
> above features.

You need to identify which API must change and what will be the ABI changes.
Then please send a deprecation notice before December 11 in order to be part
of the 2.2 release notes.

If you have some RFC patches to send (at least the API changes), it would be
a good discussion start.

Thanks