[dpdk-dev] [PATCH 5/5] add FILE arguement to debug functions
Neil Horman
nhorman at tuxdriver.com
Mon May 5 12:53:09 CEST 2014
On Sun, May 04, 2014 at 01:17:50PM -0700, Stephen Hemminger wrote:
> On Sun, 4 May 2014 08:20:54 -0400
> Neil Horman <nhorman at tuxdriver.com> 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 <stephen at networkplumber.org>
> > >
> > 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.
>
Why not? Looking at it it seems to me that you could get this exact same
functionality by calling rte_openlog_stream(stdout);
Neil
More information about the dev
mailing list