From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id B50C02A5E for ; Fri, 3 Mar 2017 16:54:05 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga105.jf.intel.com with ESMTP; 03 Mar 2017 07:54:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,237,1484035200"; d="scan'208";a="830582847" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by FMSMGA003.fm.intel.com with ESMTP; 03 Mar 2017 07:54:04 -0800 Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 3 Mar 2017 07:54:04 -0800 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.17]) by FMSMSX157.amr.corp.intel.com ([169.254.14.122]) with mapi id 14.03.0248.002; Fri, 3 Mar 2017 07:54:03 -0800 From: "Wiles, Keith" To: Pascal Mazon CC: "dev@dpdk.org" Thread-Topic: [PATCH 0/4] net/tap: support flow API Thread-Index: AQHSlAtuupZVGHthK0SNkAfhyQaBEKGDysYA Date: Fri, 3 Mar 2017 15:54:03 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.49.209] Content-Type: text/plain; charset="us-ascii" Content-ID: <5409A61E6B4388448A262C783DAFE4F8@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 0/4] net/tap: support flow API 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: Fri, 03 Mar 2017 15:54:06 -0000 > On Mar 3, 2017, at 4:45 AM, Pascal Mazon wrote: >=20 > This series add support for the flow API in tap PMD. >=20 > It enables filtering specific packets incoming on the tap netdevice, to > process only desired ones. Under the hood, it uses kernel TC (traffic > control), which takes place very early in the stack, and supports most > common pattern items and actions defined in the flow API. >=20 > This series applies on top of: >=20 > [PATCH 0/6] net/tap: add additional management ops >=20 > Pascal Mazon (4): > net/tap: move private elements to external header > net/tap: add preliminary support for rte_flow > net/tap: add netlink back-end for flow API > net/tap: add basic flow API patterns and actions >=20 > doc/guides/nics/features/tap.ini | 1 + > drivers/net/tap/Makefile | 39 ++ > drivers/net/tap/rte_eth_tap.c | 73 +-- > drivers/net/tap/tap.h | 76 +++ > drivers/net/tap/tap_flow.c | 1050 +++++++++++++++++++++++++++++++++= +++++ > drivers/net/tap/tap_flow.h | 58 +++ > drivers/net/tap/tap_netlink.c | 367 +++++++++++++ > drivers/net/tap/tap_netlink.h | 69 +++ > drivers/net/tap/tap_tcmsgs.c | 378 ++++++++++++++ > drivers/net/tap/tap_tcmsgs.h | 63 +++ > 10 files changed, 2140 insertions(+), 34 deletions(-) > create mode 100644 drivers/net/tap/tap.h > create mode 100644 drivers/net/tap/tap_flow.c > create mode 100644 drivers/net/tap/tap_flow.h > create mode 100644 drivers/net/tap/tap_netlink.c > create mode 100644 drivers/net/tap/tap_netlink.h > create mode 100644 drivers/net/tap/tap_tcmsgs.c > create mode 100644 drivers/net/tap/tap_tcmsgs.h A lot of great changes to the TAP PMD here, but I did not see the tap.rst f= ile getting updated to include the new remote option and other items you se= e fit to add to the docs. >=20 > --=20 > 2.8.0.rc0 >=20 Regards, Keith