From: Panu Matilainen <pmatilai@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: 2.3 Roadmap
Date: Tue, 1 Dec 2015 16:27:58 +0200 [thread overview]
Message-ID: <565DAE6E.5040102@redhat.com> (raw)
In-Reply-To: <20151201100333.GA32252@bricha3-MOBL3>
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 -
next prev parent reply other threads:[~2015-12-01 14:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 20:50 2.3 Roadmap O'Driscoll, Tim
2015-11-30 21:50 ` Thomas Monjalon
2015-11-30 22:19 ` Dave Neary
2015-12-01 11:57 ` O'Driscoll, Tim
2015-11-30 22:30 ` Hobywan Kenoby
2015-12-01 11:52 ` O'Driscoll, Tim
2015-11-30 22:53 ` Kyle Larose
2015-12-01 1:16 ` Stephen Hemminger
2015-12-01 10:03 ` Bruce Richardson
2015-12-01 11:26 ` Yoshinobu Inoue
2015-12-01 11:58 ` Bruce Richardson
2015-12-01 13:42 ` Matthew Hall
2015-12-01 14:45 ` Kyle Larose
2015-12-01 19:28 ` Matthew Hall
2015-12-02 0:53 ` Yoshinobu Inoue
2015-12-01 14:27 ` Panu Matilainen [this message]
2015-12-01 14:48 ` Vincent JARDIN
2015-12-01 14:58 ` Panu Matilainen
2015-12-01 15:16 ` Christian Ehrhardt
2015-12-01 15:19 ` Bruce Richardson
2015-12-01 15:31 ` Aaron Conole
2015-12-01 15:54 ` Richardson, Bruce
2015-12-02 1:38 ` Wiles, Keith
2015-12-02 2:42 ` Matthew Hall
2015-12-01 19:32 ` Matthew Hall
2015-12-02 11:24 ` Neil Horman
2015-12-01 12:59 ` Matthew Hall
2015-12-01 13:16 ` O'Driscoll, Tim
2015-12-01 13:44 ` Matthew Hall
2015-12-01 13:57 ` Bruce Richardson
2015-12-01 19:49 ` Matthew Hall
2015-12-02 12:35 ` Bruce Richardson
2015-12-02 15:47 ` Matthew Hall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=565DAE6E.5040102@redhat.com \
--to=pmatilai@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.