From mboxrd@z Thu Jan  1 00:00:00 1970
From: Panu Matilainen <pmatilai@redhat.com>
Subject: Re: 2.3 Roadmap
Date: Tue, 1 Dec 2015 16:27:58 +0200
Message-ID: <565DAE6E.5040102@redhat.com>
References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674705F1@IRSMSX108.ger.corp.intel.com>
 <D76BBBCF97F57144BB5FCF08007244A7311148B3@wtl-exchp-2.sandvine.com>
 <20151130171655.70e4ce25@xeon-e3> <20151201100333.GA32252@bricha3-MOBL3>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
To: Bruce Richardson <bruce.richardson@intel.com>,
 Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id 361F38D89
 for <dev@dpdk.org>; Tue,  1 Dec 2015 15:28:01 +0100 (CET)
In-Reply-To: <20151201100333.GA32252@bricha3-MOBL3>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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 <klarose@sandvine.com> wrote:
>>
>>> Hi Tim,
>>>
>>> On Mon, Nov 30, 2015 at 3:50 PM, O'Driscoll, Tim <tim.odriscoll@intel.com> 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 -