On 21.03.2018 18:37, Ben Pfaff wrote:
> On Wed, Mar 21, 2018 at 06:25:11PM +0300, Ilya Maximets 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()':
Ilya Maximets writes:
> 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 ar
On Wed, Mar 21, 2018 at 06:25:11PM +0300, Ilya Maximets 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 allocat
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 e
