[ovs-git] [openvswitch/ovs] c1c698: docs: Update supported DPDK versions.

GitHub noreply at github.com
Sat Mar 31 18:17:00 UTC 2018

  Branch: refs/heads/branch-2.8
  Home:   https://github.com/openvswitch/ovs
  Commit: c1c69886516a159f8fae11aecababea2f7d9969b
  Author: Ian Stokes <ian.stokes at intel.com>
  Date:   2018-03-21 (Wed, 21 Mar 2018)

  Changed paths:
    M Documentation/faq/releases.rst

  Log Message:
  docs: Update supported DPDK versions.

Update the OVS to DPDK release table to use DPDK 16.11.x for
OVS 2.7. This will avoid future documentation updates for the
2.8 branch with regards to supported DPDK versions for OVS 2.7.

Signed-off-by: Ian Stokes <ian.stokes at intel.com>
Acked-by: Kevin Traynor <ktraynor at redhat.com>

  Commit: 86ffff0f488136c5bc690d9a432fdc464ca3b432
  Author: Kevin Traynor <ktraynor at redhat.com>
  Date:   2018-03-23 (Fri, 23 Mar 2018)

  Changed paths:
    M lib/netdev-dpdk.c

  Log Message:
  netdev-dpdk: Remove 'error' from non error log.

Presently, if OVS tries to setup more queues than
are allowed by a specific NIC, OVS will handle
this case by retrying with a lower amount of queues.

Rather than reporting initial failed queue setups
in the logs as ERROR, they are reported as INFO but
contain the word 'error'. Unless a user has detailed
knowledge of OVS-DPDK workings, this is confusing.

Let's remove 'error' from the INFO log.

Signed-off-by: Kevin Traynor <ktraynor at redhat.com>
Signed-off-by: Ian Stokes <ian.stokes at intel.com>

  Commit: 3c70cfdff390ea8f300bde9e76fce68cccca4e68
  Author: Ilya Maximets <i.maximets at samsung.com>
  Date:   2018-03-23 (Fri, 23 Mar 2018)

  Changed paths:
    M lib/dpdk.c

  Log Message:
  netdev-dpdk: Limit rate of DPDK logs.

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>
Acked-by: Aaron Conole <aconole at redhat.com>
Signed-off-by: Ian Stokes <ian.stokes at intel.com>

Compare: https://github.com/openvswitch/ovs/compare/165962794098...3c70cfdff390

More information about the git mailing list