[dpdk-dev] Where is the Kernel NIC interface example in the source code?

[dpdk-dev] Where is the Kernel NIC interface example in the source code?

[Peter Chen]

[-- Attachment #1: Type: text/plain, Size: 171 bytes --]

This is in the sample application guide. I want to use tcpdump on the dpdk
port, however its not in the examples folder of the source code...was it
accidentally left out?

[-- Attachment #2: Type: text/html, Size: 196 bytes --]

Re: [dpdk-dev] Where is the Kernel NIC interface example in the source code?

[Stephen Hemminger]

On Wed, 26 Jun 2013 16:54:06 -0700
Peter Chen <peter.feifan.chen@gmail.com> wrote:

> This is in the sample application guide. I want to use tcpdump on the dpdk
> port, however its not in the examples folder of the source code...was it
> accidentally left out?

When you use DPDK, the application gets raw control over the hardware.
The kernel device (used by tcpdump) is gone. Since it is a pure application
with responsibility for everything, you could write a capture application
that writes a pcap format file. Part of the downside of something like DPDK
is that sharing device with system is hard.

Re: [dpdk-dev] Where is the Kernel NIC interface example in the source code?

[Thomas Monjalon]

27/06/2013 01:54, Peter Chen :
> This is in the sample application guide. I want to use tcpdump on the dpdk
> port, however its not in the examples folder of the source code...was it
> accidentally left out?

The doc you are reading is about DPDK 1.3.1. The source code is not yet 
released on dpdk.org but it should happen soon.

-- 
Thomas

Re: [dpdk-dev] Where is the Kernel NIC interface example in the source code?

[Antti Kantee]

On 27.6.2013 2:54, Peter Chen wrote:
> This is in the sample application guide. I want to use tcpdump on the dpdk
> port, however its not in the examples folder of the source code...was it
> accidentally left out?

If you run a rump kernel on top of dpdk, hijacking the normal tcpdump 
binary against the rump kernel should work in theory.  I say "in theory" 
because:

1) the rump kernel dpdk driver not contain support.  ok, it's literally 
two lines of code, but it's still currently theoretical
2) there might be some disagreement with ioctl's and bpf format between 
the Linux userland and NetBSD kernel, requiring some further hacking

Of course, if you don't want TCP/IP at all, the benefit is also 
theoretical ;)

   - antti