>When using multiple PMDs and numerous ports, a performance gain
>may be achieved in some use cases by pinning a PMD/port to a
>particular (set of) core(s).
>
>This patch provides a summary of the switch's port/core affinities
>each time that the status of the switch's ports is modified.
>Based on this information, a user may determine what affinity
>modifications are required to optimise performance for their
>particular use case.
>
>Signed-off-by: Mark Kavanagh <mark.b.kavan...@intel.com>
>Signed-off-by: Wojciech Andralojc <wojciechx.andral...@intel.com>
>---
> lib/dpif-netdev.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
>diff --git a/lib/dpif-netdev.c b/lib/dpif-netdev.c
>index 7df9523..17a6c08 100644
>--- a/lib/dpif-netdev.c
>+++ b/lib/dpif-netdev.c
>@@ -2664,6 +2664,11 @@ reload:
>     emc_cache_init(&pmd->flow_cache);
>     poll_cnt = pmd_load_queues(pmd, &poll_list, poll_cnt);
>
>+    /* List port/core affinity */
>+    for (i = 0; i < poll_cnt; i++) {
>+       VLOG_INFO("Core %d processing port \'%s\'\n", pmd->core_id,
>netdev_get_name(poll_list[i].port->netdev));
>+    }
>+
>     /* Signal here to make sure the pmd finishes
>      * reloading the updated configuration. */
>     dp_netdev_pmd_reload_done(pmd);
>--
>1.9.3

Are there any outstanding issues with this patch that might prevent it from 
being upstreamed?

Any feedback would be appreciated.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to