From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 3A0D0FC1A for ; Thu, 30 Mar 2017 02:57:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490835477; x=1522371477; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ZALAg5nXDOMrwE3JXaNEFm1NdsXKm+EziM9IM/0vdcM=; b=CmMK7zlliA+OPU6y63fZQjkge9V6DIGqPGYoWVwMCitfRJt25uTUp2OW aQxGHuiLGMbqQs21Dx0niiwLV7JzFw==; Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Mar 2017 17:57:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,244,1486454400"; d="scan'208";a="82105490" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga005.fm.intel.com with ESMTP; 29 Mar 2017 17:57:55 -0700 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 29 Mar 2017 17:57:55 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 29 Mar 2017 17:57:55 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.212]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.82]) with mapi id 14.03.0248.002; Thu, 30 Mar 2017 08:57:52 +0800 From: "Lu, Wenzhuo" To: "Iremonger, Bernard" , "dev@dpdk.org" , "Xing, Beilei" , "Wu, Jingjing" CC: "Zhang, Helin" , "Stroe, Laura" Thread-Topic: [PATCH v4 2/5] net/i40e: add QinQ filter create function Thread-Index: AQHSqKtxM3TcNVMarkmpneJld7KVx6Gsj5ag Date: Thu, 30 Mar 2017 00:57:51 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B584ADB@shsmsx102.ccr.corp.intel.com> References: <1490718059-380-1-git-send-email-bernard.iremonger@intel.com> <1490805709-11997-3-git-send-email-bernard.iremonger@intel.com> In-Reply-To: <1490805709-11997-3-git-send-email-bernard.iremonger@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 Subject: Re: [dpdk-dev] [PATCH v4 2/5] net/i40e: add QinQ filter create function X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 00:57:57 -0000 Hi, > -----Original Message----- > From: Iremonger, Bernard > Sent: Thursday, March 30, 2017 12:42 AM > To: dev@dpdk.org; Xing, Beilei; Wu, Jingjing > Cc: Zhang, Helin; Lu, Wenzhuo; Iremonger, Bernard; Stroe, Laura > Subject: [PATCH v4 2/5] net/i40e: add QinQ filter create function >=20 > Add i40e_cloud_filter_qinq_create function, and call it from > i40e_dev_consistent_tunnel_filter_set function. > Replace the Outer IP filter with the QinQ filter. >=20 > QinQ allows multiple VLAN tags to be inserted into a single Ethernet fram= e. > A QinQ frame is a frame that has two VLAN 802.1Q headers. > 802.1Q tunneling (QinQ) is a technique often used by Metro Ethernet > providers as a layer 2 VPN for customers. >=20 > Signed-off-by: Laura Stroe > Signed-off-by: Bernard Iremonger Acked-by: Wenzhuo Lu