From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: Proposal: enable redirection of DPDK logs from the user app Date: Wed, 5 Oct 2016 14:22:38 -0700 Message-ID: <20161005212238.GA7284@mhcomputing.net> References: <32054c5dd466431ebf99d84641c6313a@bilemail1.empirix.com> <4b3ed268f2584b4aaf251ba39f8c90bf@bilemail1.empirix.com> <348c536dca594a3fbd38137e2a5a29aa@bilemail1.empirix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Olivier Matz , "dev@dpdk.org" To: "Montorsi, Francesco" Return-path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id 3659C2A58 for ; Wed, 5 Oct 2016 23:22:39 +0200 (CEST) Content-Disposition: inline In-Reply-To: <348c536dca594a3fbd38137e2a5a29aa@bilemail1.empirix.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.