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' and the DPDK error code from
the INFO log.
Signed-off-by: Kevin Traynor <ktray...@redhat.com>
---
lib/netdev-dpdk.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c
index af9843a..2032712 100644
--- a/lib/netdev-dpdk.c
+++ b/lib/netdev-dpdk.c
@@ -729,6 +729,6 @@ dpdk_eth_dev_queue_setup(struct netdev_dpdk *dev, int
n_rxq, int n_txq)
dev->socket_id, NULL);
if (diag) {
- VLOG_INFO("Interface %s txq(%d) setup error: %s",
- dev->up.name, i, rte_strerror(-diag));
+ VLOG_INFO("Interface %s unable to setup txq(%d)",
+ dev->up.name, i);
break;
}
@@ -745,6 +745,6 @@ dpdk_eth_dev_queue_setup(struct netdev_dpdk *dev, int
n_rxq, int n_txq)
dev->socket_id, NULL, dev->mp);
if (diag) {
- VLOG_INFO("Interface %s rxq(%d) setup error: %s",
- dev->up.name, i, rte_strerror(-diag));
+ VLOG_INFO("Interface %s unable to setup rxq(%d)",
+ dev->up.name, i);
break;
}
--
1.8.3.1
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
