[ovs-git] [openvswitch/ovs] e77c97: dpif-netdev: Add round-robin based rxq to pmd assi...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/openvswitch/ovs
  Commit: e77c97b9d693a96349af68c37c561252d8d7dcb8
      https://github.com/openvswitch/ovs/commit/e77c97b9d693a96349af68c37c561252d8d7dcb8
  Author: Kevin Traynor <ktraynor at redhat.com>
  Date:   2018-09-14 (Fri, 14 Sep 2018)

  Changed paths:
    M Documentation/topics/dpdk/pmd.rst
    M NEWS
    M lib/dpif-netdev.c
    M tests/pmd.at
    M vswitchd/vswitch.xml

  Log Message:
  -----------
  dpif-netdev: Add round-robin based rxq to pmd assignment.

Prior to OVS 2.9 automatic assignment of Rxqs to PMDs
(i.e. CPUs) was done by round-robin.

That was changed in OVS 2.9 to ordering the Rxqs based on
their measured processing cycles. This was to assign the
busiest Rxqs to different PMDs, improving aggregate
throughput.

For the most part the new scheme should be better, but
there could be situations where a user prefers a simple
round-robin scheme because Rxqs from a single port are
more likely to be spread across multiple PMDs, and/or
traffic is very bursty/unpredictable.

Add 'pmd-rxq-assign' config to allow a user to select
round-robin based assignment.

Signed-off-by: Kevin Traynor <ktraynor at redhat.com>
Acked-by: Eelco Chaudron <echaudro at redhat.com>
Acked-by: Ilya Maximets <i.maximets at samsung.com>
Signed-off-by: Ian Stokes <ian.stokes at intel.com>


  Commit: d9564a2fcc90f0b9de507ad1e1a540c5d9a48684
      https://github.com/openvswitch/ovs/commit/d9564a2fcc90f0b9de507ad1e1a540c5d9a48684
  Author: Ben Pfaff <blp at ovn.org>
  Date:   2018-09-17 (Mon, 17 Sep 2018)

  Changed paths:
    M Documentation/topics/dpdk/pmd.rst
    M NEWS
    M lib/dpif-netdev.c
    M tests/pmd.at
    M vswitchd/vswitch.xml

  Log Message:
  -----------
  Merge branch 'dpdk_merge' of https://github.com/istokes/ovs into HEAD


Compare: https://github.com/openvswitch/ovs/compare/9539528def95...d9564a2fcc90
      **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.