From: Antti Kantee <pooka@iki.fi>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Where is the Kernel NIC interface example in the source code?
Date: Fri, 28 Jun 2013 17:05:20 +0300 [thread overview]
Message-ID: <51CD9820.1020606@iki.fi> (raw)
In-Reply-To: <CAMGYKAdADf0Z=Ld7vY_G6LXQGWm=dg9toEoExO0wOZy8E=H+Wg@mail.gmail.com>
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
prev parent reply other threads:[~2013-06-28 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 23:54 Peter Chen
2013-06-27 0:21 ` Stephen Hemminger
2013-06-27 16:20 ` Thomas Monjalon
2013-06-28 14:05 ` Antti Kantee [this message]
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=51CD9820.1020606@iki.fi \
--to=pooka@iki.fi \
--cc=dev@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).