From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH 5/5] add FILE arguement to debug functions Date: Sun, 4 May 2014 13:17:50 -0700 Message-ID: <20140504131750.45409335@nehalam.linuxnetplumber.net> References: <20140502234251.707598579@vyatta.com> <20140502234407.841791092@vyatta.com> <20140504122053.GA5012@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Neil Horman Return-path: In-Reply-To: <20140504122053.GA5012-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Sun, 4 May 2014 08:20:54 -0400 Neil Horman wrote: > On Fri, May 02, 2014 at 04:42:56PM -0700, Stephen Hemminger wrote: > > The DPDK dump functions are useful for remote debugging of an > > applications. But when application runs as a daemon, stdout > > is typically routed to /dev/null. > > > > Instead change all these functions to take a stdio FILE * handle > > instead. An application can then use open_memstream() to capture > > the output. > > > > Signed-off-by: Stephen Hemminger > > > Why not convert these to rte_log calls? Seems like we already have the > infrastrucutre here, we just need to use it. > Neil > Because it is useful to have remote console like functionatlity, and dumping this to log doesn't work for that.