From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <rahul.lakkireddy@chelsio.com> Received: from stargate3.asicdesigners.com (stargate.chelsio.com [12.32.117.8]) by dpdk.org (Postfix) with ESMTP id 8A6928DB4 for <dev@dpdk.org>; Wed, 2 Dec 2015 09:05:12 +0100 (CET) Received: from localhost (scalar.blr.asicdesigners.com [10.193.185.94]) by stargate3.asicdesigners.com (8.13.8/8.13.8) with ESMTP id tB2857mX027295; Wed, 2 Dec 2015 00:05:08 -0800 Date: Wed, 2 Dec 2015 13:35:04 +0530 From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> To: Thomas Monjalon <thomas.monjalon@6wind.com> Message-ID: <20151202080502.GA7710@scalar.blr.asicdesigners.com> References: <20151130124943.GA15383@scalar.blr.asicdesigners.com> <2318875.uXDYP4N6Nj@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2318875.uXDYP4N6Nj@xps13> User-Agent: Mutt/1.5.24 (2015-08-30) Cc: "dev@dpdk.org" <dev@dpdk.org>, Felix Marti <felix@chelsio.com>, Nirranjan Kirubaharan <nirranjan@chelsio.com>, Kumar A S <kumaras@chelsio.com> Subject: Re: [dpdk-dev] Query on Filtering Support in DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list 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> X-List-Received-Date: Wed, 02 Dec 2015 08:05:13 -0000 Hi Thomas, On Monday, November 11/30/15, 2015 at 05:43:18 -0800, Thomas Monjalon wrote: > 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. I am currently identifying the various API changes to support this and also the ABI changes if any. > > If you have some RFC patches to send (at least the API changes), it would be > a good discussion start. I will try to post some RFC patches in 3-4 days time to get more inputs/reviews on the approach. Thanks, Rahul.