[dpdk-dev] [PATCH 01/11] ixgbe: clean log messages

David Marchand david.marchand at 6wind.com
Fri Aug 29 09:45:29 CEST 2014

On Wed, Aug 27, 2014 at 8:06 PM, Stephen Hemminger <
stephen at networkplumber.org> wrote:

> On Wed, 27 Aug 2014 08:53:46 -0500
> Jay Rolette <rolette at infiniteio.com> wrote:
> > The updated output is definitely an improvement, but if you'll go with
> the
> > first solution you described (adding \n in the log macro), it works much
> > better for products using DPDK. For developer use, I think it ends up
> being
> > a wash either way.
> Also for driver consistency, all drivers must do the same thing. I.e the
> macro should either add or not add newline in the same way in all drivers.
> I fixed virtio and vmxnet3 by just taking extra newlines out of messages
> and leaving the macro alone.

Not sure that we can talk about consistency at the moment ... (all the more
so as if you only fixed two pmds).

If we go with this approach, there is still something that won't work.
ixgbe shared code uses DEBUGOUT* macros which are called a lot in this
shared code.
The macros call sites use trailing \n.
I suppose I will have a big NO from Intel guys if I remove the trailing \n,
so I suppose we can use an alternate macro that calls RTE_LOG rather than
PMD_DRV_LOG in ixgbe_os_dep.h.

I will also remove any reference to DEBUGOUT* in non-shared code.
>From my point of view, these macro are only here for compat with shared

By the way, did you look at the other patches of this series ?

I want to send a v2 later (maybe not today), so any comment on the other
patches are welcome.

David Marchand

More information about the dev mailing list