From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: 2.3 Roadmap Date: Mon, 30 Nov 2015 17:16:55 -0800 Message-ID: <20151130171655.70e4ce25@xeon-e3> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674705F1@IRSMSX108.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" To: Kyle Larose Return-path: Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by dpdk.org (Postfix) with ESMTP id E40A58D91 for ; Tue, 1 Dec 2015 02:16:46 +0100 (CET) Received: by pacdm15 with SMTP id dm15so202656734pac.3 for ; Mon, 30 Nov 2015 17:16:46 -0800 (PST) In-Reply-To: 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, 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.