From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: 2.3 Roadmap Date: Tue, 1 Dec 2015 10:03:33 +0000 Message-ID: <20151201100333.GA32252@bricha3-MOBL3> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674705F1@IRSMSX108.ger.corp.intel.com> <20151130171655.70e4ce25@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" To: Stephen Hemminger Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id EBA12E72 for ; Tue, 1 Dec 2015 11:03:54 +0100 (CET) Content-Disposition: inline In-Reply-To: <20151130171655.70e4ce25@xeon-e3> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Nov 30, 2015 at 05:16:55PM -0800, Stephen Hemminger wrote: > On Mon, 30 Nov 2015 22:53:50 +0000 > Kyle Larose wrote: > > > Hi Tim, > > > > On Mon, Nov 30, 2015 at 3:50 PM, O'Driscoll, Tim wrote: > > > > > Tcpdump Support: Support for tcpdump will be added to DPDK. This will improve usability and debugging of DPDK applications. > > > > I'm curious about the proposed tcpdump support. Is there a concrete plan for this, or is that still being looked into? Sandvine is interested in contributing to this effort. Anything we can do to help? > > > > Thanks, > > > > Kyle > > We discussed an Ovscon doing a simple example of how to have a thread use named pipe > support (already in tcpdump and wireshark). More complex solutions require changes to > libpcap and application interaction. Our current thinking is to use kni to mirror packets into the kernel itself, so that all standard linux capture tools can then be used. /Bruce