From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org, Morten B <mb@smartsharesystems.com>
Subject: Re: [dpdk-dev] tcpdump support in DPDK 2.3
Date: Mon, 14 Dec 2015 11:14:42 -0800 [thread overview]
Message-ID: <20151214111442.6328dde9@xeon-e3> (raw)
In-Reply-To: <20151214182931.GA17279@mhcomputing.net>
On Mon, 14 Dec 2015 13:29:31 -0500
Matthew Hall <mhall@mhcomputing.net> wrote:
> FYI your last name comes in as a corrupt character for me. You might have to
> think about converting it from ISO 8859-1 / 8859-15 to UTF-8.
>
> On Mon, Dec 14, 2015 at 10:57:10AM +0100, Morten B wrote:
> > Check out the new "extcap" feature of Wireshark. It uses named pipes for the
> > packets, already mentioned by Stephen Hemminger.
>
> I looked at it a bit. I wasn't 100% clear if there is a way to pass down the
> BPF expression for compilation and usage inside the DPDK application.
>
> > Tcpdump is an open source application, so it should be possible to define an
> > efficient interface between DPDK and tcpdump, and implement it in both DPDK
> > and tcpdump. The same goes for libpcap.
>
> Easier said than done. A whole ton of libpcap assumes it's talking to a very
> specific kernel interface, and the code is quite complicated.
>
> > It possibly also has a secondary feature: passing a BPF program
> > from tcpdump/libpcap to DPDK, so packets can be filtered in DPDK and don't
> > need to be passed on to tcpdump/libpcap.
>
> If we can figure out how to get this feature to work in extcap, I think that
> will be the winning solution by far.
>
> > [A]dd a BPF library (librte_bpf) to DPDK, preferably with a compiler. The
> > application initially calls the library's BPF compiler function once with
> > the BPF program to compile it, and in the fast path the application calls a
> > library function that takes an mbuf and the compiled BPF program and returns
> > an integer value indicating how many bytes of the packet should be mirrored
> > by the capturing application. +1 to Matthew Hall for taking this direction!
There are already several BPF libraries available. I would prefer DPDK not
start copying existing code.
next prev parent reply other threads:[~2015-12-14 19:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 9:57 Morten Brørup
2015-12-14 15:45 ` Aaron Conole
2015-12-14 15:48 ` Thomas Monjalon
2015-12-14 18:29 ` Matthew Hall
2015-12-14 19:14 ` Stephen Hemminger [this message]
2015-12-14 22:23 ` Matthew Hall
2015-12-14 19:17 ` Aaron Conole
2015-12-14 21:29 ` Kyle Larose
2015-12-14 22:36 ` Matthew Hall
2015-12-16 10:45 ` Bruce Richardson
2015-12-16 11:37 ` Arnon Warshavsky
2015-12-16 11:56 ` Morten Brørup
2015-12-16 11:40 ` Morten Brørup
2015-12-16 11:56 ` Bruce Richardson
2015-12-16 12:26 ` Morten Brørup
2015-12-16 13:12 ` Bruce Richardson
2015-12-16 22:45 ` Morten Brørup
2015-12-16 23:38 ` Matthew Hall
2015-12-17 5:59 ` Arnon Warshavsky
2015-12-16 18:15 ` Matthew Hall
2015-12-21 15:39 ` Bruce Richardson
2015-12-21 16:08 ` Morten Brørup
2015-12-21 16:17 ` Gray, Mark D
2015-12-21 17:22 ` Matthew Hall
2015-12-21 16:11 ` Gray, Mark D
2015-12-14 22:25 ` 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=20151214111442.6328dde9@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=mhall@mhcomputing.net \
/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).