Enabling NIC Multi-Queue

Scenarios

Single-core CPU performance cannot meet the requirement of processing NIC interruptions incurred with the increase of network I/O bandwidth. NIC multi-queue enables multiple CPUs to process ECS NIC interruptions, thereby improving packets per second (PPS) and I/O performance.

Support of NIC Multi-Queue

NIC multi-queue can be enabled on an ECS only when the ECS specifications, virtualization type, and image OS meet the requirements described in this section.

• For details about the ECS specifications that support NIC multi-queue, see x86 ECS Specifications and Types.
  

  If the number of NIC queues is greater than 1, NIC multi-queue is supported.

• The virtualization type must be KVM.
• The Linux public images listed in Table 2 support NIC multi-queue.
  

  • The PV driver of a Windows ECS dynamically adjusts the number of NIC queues based on the number of vCPUs of the ECS, and you do not need to set the number of Windows NIC multi-queues.
  • Public images that contain Windows Server 2008 are no longer available. However, you can still use private images that contain Windows Server 2008.
  • It is a good practice to upgrade the kernel version of the Linux ECS to 2.6.35 or later. Otherwise, NIC multi-queue is not supported.

    Run the uname -r command to obtain the kernel version. If the kernel version is earlier than 2.6.35, contact customer service to upgrade the kernel.

Importing the External Image File to the IMS Console

Setting NIC Multi-Queue for the Image

Windows OSs have not commercially supported NIC multi-queue. If you enable NIC multi-queue in a Windows image, starting an ECS created using such an image may be slow.

Use one of the following methods to set the NIC multi-queue attribute:

Method 3: Add hw_vif_multiqueue_enabled to an image through the API.

1. For instructions about how to obtain the token, see Calling APIs > Authentication in Image Management Service API Reference.
2. For instructions about how to call an API to update image information, see "Updating Image Information (Native OpenStack API)" in Image Management Service API Reference.
3. Add X-Auth-Token to the request header.

   The value of X-Auth-Token is the token obtained in step 1.

4. Add Content-Type to the request header.

   The value of Content-Type is application/openstack-images-v2.1-json-patch.

   The request URI is in the following format:

   PATCH /v2/images/{image_id}

   The request body is as follows:

   [       
            { 
             "op":"add",
             "path":"/hw_vif_multiqueue_enabled", 
             "value": "true" 
            } 
    ]

   Figure 1 shows an example request body for modifying the NIC multi-queue attribute.

   Figure 1 Example request body
   

Creating an ECS Using a Private Image

Viewing the Number of Queues of the NIC

Example:

[root@localhost ~]# ethtool -l eth0  #View the number of queues used by NIC eth0.
Channel parameters for eth0:
Pre-set maximums:
RX:               0
TX:               0
Other:                  0
Combined: 4  #Indicates that a maximum of four queues can be enabled for the NIC.
Current hardware settings:
RX:               0
TX:               0
Other:                  0
Combined: 1 #Indicates that four queues have been enabled.