[ovs-dev] [PATCH] dpif-netdev: log rxq assignment in isolated pmd
Gowrishankar Muthukrishnan
gmuthukr at redhat.com
Tue Oct 22 07:55:08 UTC 2019
There is no log about isolated rxq assigment in a pmd today, which
sometimes could be useful to trace rxq/pmd pinning, when debugging
with log. Ovs-appctl dpif-netdev/pmd-rxq-show reports about it
already, but logging is helpful to trace pinning in time.
Reported-at: https://bugzilla.redhat.com/1728616
Signed-off-by: Gowrishankar Muthukrishnan <gmuthukr at redhat.com>
---
lib/dpif-netdev.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/dpif-netdev.c b/lib/dpif-netdev.c
index 4546b55e8..7a5afea00 100644
--- a/lib/dpif-netdev.c
+++ b/lib/dpif-netdev.c
@@ -4573,6 +4573,10 @@ rxq_scheduling(struct dp_netdev *dp, bool pinned) OVS_REQUIRES(dp->port_mutex)
q->pmd = pmd;
pmd->isolated = true;
dp_netdev_pmd_unref(pmd);
+ VLOG_INFO("Core %d on numa node %d assigned port \'%s\' "
+ "rx queue %d.", pmd->core_id, numa_id,
+ netdev_rxq_get_name(q->rx),
+ netdev_rxq_get_queue_id(q->rx));
}
} else if (!pinned && q->core_id == OVS_CORE_UNSPEC) {
uint64_t cycle_hist = 0;
--
2.17.2
More information about the dev
mailing list