[ovs-dev] [PATCH v2] netdev-dpdk: Limit rate of DPDK logs.

Stokes, Ian ian.stokes at intel.com
Fri Mar 23 12:57:04 UTC 2018


> On 23.03.2018 15:18, Stokes, Ian wrote:
> >> DPDK could produce huge amount of logs. For example, in case of
> >> exhausting of a mempool in vhost-user port, following message will be
> >> printed on each call to 'rte_vhost_dequeue_burst()':
> >>
> >>     |ERR|VHOST_DATA: Failed to allocate memory for mbuf.
> >>
> >> These messages are increasing ovs-vswitchd.log size extremely fast
> >> making it unreadable and non-parsable by a common linux utils like
> >> grep, less etc. Moreover continuously growing log could exhaust the
> >> HDD space in a few hours breaking normal operation of the whole system.
> >>
> >> To avoid such issues, DPDK log rate limited to 600 messages per minute.
> >> This value is high, because we still want to see many big logs like
> >> vhost- user configuration sequence. The debug messages are treated
> >> separately to avoid looss of errors/warnings in case of intensive debug
> enabled in DPDK.
> >>
> >> Signed-off-by: Ilya Maximets <i.maximets at samsung.com>
> >
> > Thanks for this Ilya, LGTM.
> >
> > Do you think this is worth backporting to previous releases also, the
> same issue would be there also I assume?
> 
> Yes, sure.
> The described issue was found with 2.8 release.
> 

Ok, thanks all for the input. I'll merge this and back port for the dpdk_merge branches.

Thanks
Ian



More information about the dev mailing list