From: Matthew Hall <mhall@mhcomputing.net>
To: "Montorsi, Francesco" <fmontorsi@empirix.com>
Cc: Olivier Matz <olivier.matz@6wind.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Proposal: enable redirection of DPDK logs from the user app
Date: Wed, 5 Oct 2016 14:22:38 -0700 [thread overview]
Message-ID: <20161005212238.GA7284@mhcomputing.net> (raw)
In-Reply-To: <348c536dca594a3fbd38137e2a5a29aa@bilemail1.empirix.com>
On Wed, Oct 05, 2016 at 01:26:30PM +0000, Montorsi, Francesco wrote:
> Correct, but in my experience DPDK never creates such a long line of log message...
>
> Francesco
This comment is fatally flawed. Many of us write our applications using these
functions. I have things which hex-dump packets when certain debug levels are
enabled. Sadly my patch to add deeper levels to default DPDK was rejected, but
with that I have very detailed levels that say everything I ever do to the
packet.
Matthew.
prev parent reply other threads:[~2016-10-05 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 10:24 Montorsi, Francesco
2016-10-04 11:26 ` Olivier Matz
2016-10-04 12:28 ` Montorsi, Francesco
2016-10-05 12:18 ` Olivier Matz
2016-10-05 13:26 ` Montorsi, Francesco
2016-10-05 14:03 ` Olivier Matz
2016-10-05 21:22 ` Matthew Hall [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=20161005212238.GA7284@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=fmontorsi@empirix.com \
--cc=olivier.matz@6wind.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).