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 B00DD5932 for ; Wed, 28 May 2014 03:12:33 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 27 May 2014 18:12:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,924,1392192000"; d="scan'208";a="545877721" Received: from fmsmsx108.amr.corp.intel.com ([10.19.9.228]) by fmsmga002.fm.intel.com with ESMTP; 27 May 2014 18:12:31 -0700 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by FMSMSX108.amr.corp.intel.com (10.19.9.228) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 27 May 2014 18:12:31 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 27 May 2014 18:12:31 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.192]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.23]) with mapi id 14.03.0123.003; Wed, 28 May 2014 09:12:29 +0800 From: "Wu, Jingjing" To: Thomas Monjalon Thread-Topic: [dpdk-dev] [PATCH v2 0/4] NIC filters support for generic filter Thread-Index: AQHPdvDNbUccjvmsc0uwK9LYw6o4fJtUkOCAgACfFNCAAAN0EA== Date: Wed, 28 May 2014 01:12:28 +0000 Message-ID: <9BB6961774997848B5B42BEC655768F8A78A07@SHSMSX104.ccr.corp.intel.com> References: <1400895442-32433-1-git-send-email-jingjing.wu@intel.com> <5229759.KE0cFmJ2u6@xps13> <9BB6961774997848B5B42BEC655768F8A789C6@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <9BB6961774997848B5B42BEC655768F8A789C6@SHSMSX104.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v2 0/4] NIC filters support for generic filter 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: Wed, 28 May 2014 01:12:34 -0000 Hi, Thomas The generic you said may be different from I mentioned in last mail. You ar= e discussing whether the APIs provide for NIC filters is generic or not. Ab= out that we can use same API for a type of filter. For example, if we want = to configure ethertype filter, we can use the same API, no matter the NIC i= s 82580, i350, 82576 or 82599. We think these NICs may be most common used. -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wu, Jingjing Sent: Wednesday, May 28, 2014 8:53 AM To: Thomas Monjalon Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 0/4] NIC filters support for generic filt= er Hi, Thomas This patch is mainly about multiple NIC filters implement. It has close rel= ationship with NICs. As the patch says: NIC filters list below are implemented in this patchset: ethertype filter, syn filter, 2tuple filter and flex filter for 82580 and = i350=20 ethertype filter, syn filter, 5tuple filter for 82576 ethertype filter, syn filter and 5tuple filter for 82599 The same type filter uses the same API for the NICs list above. About the generic filter feature, how to define the "generic" is still in d= iscussing, and not included in this patch.=20 These NIC filters implemented in this patch are first step. Even without ge= neric, it also provides a way to configure these NIC filters to hardware in= DPDK PMD. -----Original Message----- From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] Sent: Wednesday, May 28, 2014 7:22 AM To: Wu, Jingjing Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 0/4] NIC filters support for generic filt= er Hi Jingjing, 2014-05-24 09:37, Jingjing Wu: > A generic filter mechanism for handling special packet is required. > It will allow filters to be set in HW when available so that specific=20 > packet may be filtered by NICs to specific descriptor queues for=20 > processing. Currently only Flow Director for Intel's 10GbE 82599=20 > devices is available. Other types of filter are not support. > NIC filters list below are implemented in this patchset: > ethertype filter, syn filter, 2tuple filter and flex filter for > 82580 and > i350 ethertype filter, syn filter, 5tuple filter for 82576 > ethertype filter, syn filter and 5tuple filter for 82599 I'd like we have a discussion about how this API is generic enough. I think many people would like to integrate drivers for other NICs in DPDK = and I'd hate to see a global rework of this API because we haven't tried to= think about it before. First, is there someone in the mailing list who knows other hardware which = could fit in this filtering feature? Thanks -- Thomas