From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 361F38D89 for ; Tue, 1 Dec 2015 15:28:01 +0100 (CET) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id 74B41C0B7AB7; Tue, 1 Dec 2015 14:28:00 +0000 (UTC) Received: from sopuli.koti.laiskiainen.org (vpn1-6-72.ams2.redhat.com [10.36.6.72]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tB1ERx0D001811; Tue, 1 Dec 2015 09:27:59 -0500 To: Bruce Richardson , Stephen Hemminger References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674705F1@IRSMSX108.ger.corp.intel.com> <20151130171655.70e4ce25@xeon-e3> <20151201100333.GA32252@bricha3-MOBL3> From: Panu Matilainen Message-ID: <565DAE6E.5040102@redhat.com> Date: Tue, 1 Dec 2015 16:27:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151201100333.GA32252@bricha3-MOBL3> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] 2.3 Roadmap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2015 14:28:01 -0000 On 12/01/2015 12:03 PM, Bruce Richardson wrote: > 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. The problem with that (unless I'm missing something here) is that KNI requires using out-of-tree kernel modules which makes it pretty much a non-option for distros. - Panu -