From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by dpdk.org (Postfix) with ESMTP id 4BB9768FD for ; Fri, 28 Jun 2013 16:05:07 +0200 (CEST) Received: from [IPv6:::1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTPS id C859B308DF4 for ; Fri, 28 Jun 2013 17:05:21 +0300 (EEST) Message-ID: <51CD9820.1020606@iki.fi> Date: Fri, 28 Jun 2013 17:05:20 +0300 From: Antti Kantee MIME-Version: 1.0 To: dev@dpdk.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Where is the Kernel NIC interface example in the source code? 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: Fri, 28 Jun 2013 14:05:07 -0000 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