From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 10AF42C74 for ; Tue, 14 Mar 2017 15:04:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1489500244; x=1521036244; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uRmx2X3c9AhWDGW39Yq+TE8hwuLlGcFFqwsnlhXRvg0=; b=If53MWz21wLKyXvjzfGXWyf+yJsuIbb56nFaP3WMtQdf8pS6p79npWZn yCaGtKaJmfn6pkrfHVTr7G0riA9nCQ==; Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Mar 2017 07:03:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,164,1486454400"; d="scan'208";a="75263833" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga005.jf.intel.com with ESMTP; 14 Mar 2017 07:03:55 -0700 Received: from fmsmsx154.amr.corp.intel.com (10.18.116.70) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 14 Mar 2017 07:03:55 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.172]) by FMSMSX154.amr.corp.intel.com ([169.254.6.37]) with mapi id 14.03.0248.002; Tue, 14 Mar 2017 07:03:54 -0700 From: "Wiles, Keith" To: Pascal Mazon CC: "dev@dpdk.org" Thread-Topic: [PATCH v4 3/4] net/tap: add netlink back-end for flow API Thread-Index: AQHSnJ1jRgIDx7e4RUCO1jLxTsZxE6GU076A Date: Tue, 14 Mar 2017 14:03:54 +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.255.28.43] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v4 3/4] net/tap: add netlink back-end for 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: Tue, 14 Mar 2017 14:04:04 -0000 > On Mar 14, 2017, at 4:29 PM, Pascal Mazon wrote: >=20 > Each kernel netdevice may have queueing disciplines set for it, which > determine how to handle the packet (mostly on egress). That's part of > the TC (Traffic Control) mechanism. >=20 > Through TC, it is possible to set filter rules that match specific > packets, and act according to what is in the rule. This is a perfect > candidate to implement the flow API for the tap PMD, as it has an > associated kernel netdevice automatically. >=20 > Each flow API rule will be translated into its TC counterpart. >=20 > To leverage TC, it is necessary to communicate with the kernel using > netlink. This patch introduces a library to help that communication. >=20 > Inside netlink.c, functions are generic for any netlink messaging. > Inside tcmsgs.c, functions are specific to deal with TC rules. >=20 > Signed-off-by: Pascal Mazon > Acked-by: Olga Shern Acked-by: Keith Wiles Regards, Keith