From: Matthew Hall <mhall@mhcomputing.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [dpdk-dev] tcpdump support in DPDK 2.3
Date: Wed, 16 Dec 2015 13:15:57 -0500 [thread overview]
Message-ID: <20151216181557.GA16963@mhcomputing.net> (raw)
In-Reply-To: <20151216115611.GB10020@bricha3-MOBL3>
On Wed, Dec 16, 2015 at 11:56:11AM +0000, Bruce Richardson wrote:
> Having this work with any application is one of our primary targets here.
> The app author should not have to worry too much about getting basic debug
> support. Even if it doesn't work at 40G small packet rates, you can get a
> lot of benefit from a scheme that provides functional debugging for an app.
I think my issue is that I don't think I buy into this particular set of
assumptions above.
I don't think a capture mechanism that doesn't work right in the real use
cases of the apps actually buys us much. If all we care about is quickly
dumping some frames to a pcap for occasional debugging, I already have some C
code for that I can donate which is a lot less complicated than the trouble
being proposed for "basic debug support". Or we could use libpcap's
equivalent... but it's quite a lot more complicated than the code I have.
If we're going to assign engineers to this it's costing somebody a lot of time
and money. So I'd prefer to get them focused on something that will always
work even with high loads, such as real bpfjit support.
Matthew.
next prev parent reply other threads:[~2015-12-16 18:15 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
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 [this message]
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=20151216181557.GA16963@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
/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).