Comment 8 for bug 1584006

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (stable/mitaka)

Reviewed: https://review.openstack.org/326392
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=260b0b8f99bdfeb784be1a0b7374cd284d3b68e9
Submitter: Jenkins
Branch: stable/mitaka

commit 260b0b8f99bdfeb784be1a0b7374cd284d3b68e9
Author: Artur Svechnikov <email address hidden>
Date: Fri May 27 17:43:24 2016 +0300

    Change CPU distribution

    CPU distribution mechanism should be changed due
    to incorect requirements to nova and dpdk CPUs allocation

    Changes:
     * Change CPU distribution
     * Add function for recognizing DPDK NICs for node
     * Remove requirement of enabled hugepages for
       DPDK NICs (it's checked before deployment)
     * Change HugePages distribution. Now it take into
       account Nova CPUs placement

    Requirements Before:
     DPDK's CPUs should be located on the same NUMAs as
     Nova CPUs

    Requirements Now:
     1. DPDK component CPU pinning has two parts:
         * OVS pmd core CPUs - These CPUs must be placed on the
           NUMAs where DPDK NIC is located. Since DPDK NIC can
           handle about 12 Mpps/s and 1 CPU can handle about
           3 Mpps/s there is no necessity to place more than
           4 CPUs per NIC. Let's name all remained CPUs as
           additional CPUs.
         * OVS Core CPUs - 1 CPU is enough and that CPU should
           be taken from any NUMA where at least 1 OVS pmd core
           CPU is located

     2. To improve Nova and DPDK performance, all additional CPUs
        should be distributed along with Nova's CPUs as
        OVS pmd core CPUs.

    Change-Id: Ib2adf39c36b2e1536bb02b07fd8b5af50e3744b2
    Closes-Bug: #1584006
    (cherry picked from commit 76e270ef966dd7735eac3e87f94bb0a39e49388c)