From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id BACB32BCD for ; Thu, 25 Feb 2016 14:48:29 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP; 25 Feb 2016 05:48:28 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,498,1449561600"; d="scan'208";a="753102541" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.64]) by orsmga003.jf.intel.com with SMTP; 25 Feb 2016 05:48:26 -0800 Received: by (sSMTP sendmail emulation); Thu, 25 Feb 2016 13:48:25 +0025 Date: Thu, 25 Feb 2016 13:48:25 +0000 From: Bruce Richardson To: Rahul Lakkireddy Message-ID: <20160225134825.GD20868@bricha3-MOBL3> References: <2131fd9284f6b25cdbb4c7885354856f4ff2ebe5.1454408702.git.rahul.lakkireddy@chelsio.com> <20160224144056.GE19616@bricha3-MOBL3> <20160224183532.GA8856@chelsio.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160224183532.GA8856@chelsio.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" , Kumar A S , Nirranjan Kirubaharan Subject: Re: [dpdk-dev] [PATCH 02/10] examples/test-cxgbe-filters: add example to test cxgbe fdir support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2016 13:48:30 -0000 On Thu, Feb 25, 2016 at 12:05:34AM +0530, Rahul Lakkireddy wrote: > Hi Bruce, > > On Wednesday, February 02/24/16, 2016 at 06:40:56 -0800, Bruce Richardson wrote: > > On Wed, Feb 03, 2016 at 02:02:23PM +0530, Rahul Lakkireddy wrote: > > > Add a new test_cxgbe_filters command line example to test support for > > > Chelsio T5 hardware filtering. Shows how to pass the Chelsio input flow > > > and input masks. Also, shows how to pass extra behavior arguments to > > > rewrite fields in matched filter rules. > > > > > > Also add documentation and update MAINTAINERS. > > > > > > Signed-off-by: Rahul Lakkireddy > > > Signed-off-by: Kumar Sanghvi > > > > Hi, > > > > for testing NIC functionality, the "testpmd" app is what is used, and it already > > contains support for existing flow director functionality. Should the testing > > functionality not be included there? > > > > We initially thought of adding example by extending flow director in > testpmd itself. However, based on discussion at [1], we then created > a separate sample app for this considering each vendor would come up > with their own sample app. > > [1] http://permalink.gmane.org/gmane.comp.networking.dpdk.devel/31471 > Thanks for the old conversation link. I don't like the idea of having vendor specific sample apps, I think the samples should be as generic as possible. If there is a particular feature that you want to demonstrate in a sample app, then that is worthy of inclusion - assuming it's possible that in future more than one vendor's hardware will support the feature. Within the documentation for the particular NIC or driver, feel free to call out what features the NIC supports and how those should be configured. I hope this makes sense. We probably need a documented policy on how to go about adding new NIC feature support to ensure everyone is in agreement on how things should be done so as to allow vendors to expose the features of their hardware, while at the same time allowing users to write applications that can be generic across the various hardware platforms. Regards, /Bruce