From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v6 1/1] net/tap: add remote netdevice traffic capture Date: Fri, 24 Mar 2017 15:48:13 +0000 Message-ID: References: <9105bd4272eca9c9ea6567a0e9b1d3235e03855a.1490258249.git.pascal.mazon@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Pascal Mazon , keith.wiles@intel.com Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id D41D8D2CC for ; Fri, 24 Mar 2017 16:48:34 +0100 (CET) In-Reply-To: <9105bd4272eca9c9ea6567a0e9b1d3235e03855a.1490258249.git.pascal.mazon@6wind.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 3/23/2017 8:42 AM, Pascal Mazon wrote: > By default, a tap netdevice is of no use when not fed by a separate > process. The ability to automatically feed it from another netdevice > allows applications to capture any kind of traffic normally destined to > the kernel stack. > > This patch implements this ability through a new optional "remote" > parameter. > > Packets matching filtering rules created with the flow API are matched > on the remote device and redirected to the tap PMD, where the relevant > action will be performed. > > Signed-off-by: Pascal Mazon > Acked-by: Olga Shern > Acked-by: Keith Wiles Applied to dpdk-next-net/master, thanks.