From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id EEFAE42F4D for ; Wed, 26 Jul 2023 09:32:41 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B3F0840E25; Wed, 26 Jul 2023 09:32:41 +0200 (CEST) Received: from mail-pg1-f175.google.com (mail-pg1-f175.google.com [209.85.215.175]) by mails.dpdk.org (Postfix) with ESMTP id CCAD140EDF for ; Wed, 26 Jul 2023 09:32:39 +0200 (CEST) Received: by mail-pg1-f175.google.com with SMTP id 41be03b00d2f7-517ab9a4a13so4534784a12.1 for ; Wed, 26 Jul 2023 00:32:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690356759; x=1690961559; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wWx7yapj2JspYOzR0Dn8y63/AIsDliPak4CV4RvUmJ8=; b=rNI+ZWfUG9iK6vavymQecU6O/fSNwbtgFkz2BtUZJp3e5BAoUn5sHmlC69H+jmFtof dK3WYYGpwtcHFU3HjTZzrcKoGl1Wp5XEfZpFJZUtgp8eYcoMO0XImdxbQ2vXrIPdvvMq 7gt7TJHRpjs2Sk7ZbI8RtfX227B7JZPSdNDv2BBNSW7N4N0B1W1h+sH84C59lUAPGcwn 9Xh7v0WTVvs4ijRU91o05TbIols7YgYW8D6CudVig2Z89VD8dM4QpyzXtrk+eTmE7rlv gRWxET+96HRRFIEUbNaf7aVMtSx7QH0te5FqfeaWm+9DEt83w3EzOj8S63Kvo6Hg7O// fa4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690356759; x=1690961559; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=wWx7yapj2JspYOzR0Dn8y63/AIsDliPak4CV4RvUmJ8=; b=NYk+PfcnxTbrdY7EB5YKUzJ7UFmv+a9tWhj3KClQt1oQ3ikXcyPw3UEk3bnlt0OXJc bxvXrlKhu9wjP96dx58H9STn4FBglf13+g+NMgKLvLA7iTaGRUuHqBA4dbb1wx9fPRBM /dBRs55wi1kNYbrKr5EW6kRVhmuwzPjgtlllxTxoVvfy52vWpOJq4hOvyaHJfrFckJA0 AUE8zMkWKxUlvTUCmatMDl3j+vKQaJJWUiTqf9PfYmClnqvYokkUFcw3xmpaWWWnKIfJ P5oojSEezWo0Xiv5Spcaun/cXJs3cEb65hABq1Psh2s9bg/r5UvNbpaewp01SC5eaYnG M8Jg== X-Gm-Message-State: ABy/qLYLT+PufOWoBz40hvKPzS8qC/aduZBTJmj1axmAM20GaMXAPSqt nl/x13byravj5RQ3qtsStj5HrL7pFaYACgzHBFg= X-Google-Smtp-Source: APBJJlGZMwdQqXRey6hcUCWMh8U8Y6AMHFmDethoOzRsT7ZChvI21LfY4Zp5HIlJ8b7fuNljiSE+RIE/o4yIEBwFxxQ= X-Received: by 2002:a17:90a:2e85:b0:268:214f:ae69 with SMTP id r5-20020a17090a2e8500b00268214fae69mr1209505pjd.35.1690356758719; Wed, 26 Jul 2023 00:32:38 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: shiv chittora Date: Wed, 26 Jul 2023 13:02:27 +0530 Message-ID: Subject: Re: Enable RSS for virtio application ( dpdk version 21.11) To: Bing Zhao Cc: "users@dpdk.org" Content-Type: multipart/alternative; boundary="00000000000025b23006015eda0c" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --00000000000025b23006015eda0c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Bing for quick response. The virtio driver version 1.0.0 is included in the Linux kernel version 4.9 that powers VM. ethtool -i eth1 driver: virtio_net version: 1.0.0 firmware-version: expansion-rom-version: bus-info: 0000:00:04.0 Nutanix document stats that "Ensure the AHV UVM is running the latest Nutanix VirtIO driver package. Nutanix VirtIO 1.1.6 or higher is required for RSS support. " Linux kernel version: 5.4 and later will have Virtio 1.1.6. Since the programme is built on the dpdk, the PMD driver will use the eth interface rather than the one that the kernel provides. I apologise if I'm mistaken. RSS is supported by the dpdk PMD version in use. Because of the client-centric nature of this application, upgrading the kernel will be challenging. Do you believe that the only option is to upgrade the vm kernel version? Thanks , Shiv On Wed, Jul 26, 2023 at 12:33=E2=80=AFPM Bing Zhao wrote= : > IIRC, the =E2=80=9CVIRTIO_NET_F_RSS=E2=80=9D is some capability reported = and decided > during the driver setup/communication stage. It is mostly like that your > libs/drivers running on the host for the VM does not support this feature= . > > Have you tried to update the versions of VM or the package/lib of VirtIO > for this VM? > > > > *From:* shiv chittora > *Sent:* Wednesday, July 26, 2023 1:05 PM > *To:* users@dpdk.org > *Subject:* Enable RSS for virtio application ( dpdk version 21.11) > > > > *External email: Use caution opening links or attachments* > > > > I'm using a Nutanix virtual machine to run a DPDK(Version 21.11)-based > application. > Application is failing during rte_eth_dev_configure . For our application= , > RSS support is required. > > eth_config.rxmode.mq_mode =3D ETH_MQ_RX_RSS; > static uint8_t hashKey[] =3D { > 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, > 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, > 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, > 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, > 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, > }; > > eth_config.rx_adv_conf.rss_conf.rss_key =3D hashKey; > eth_config.rx_adv_conf.rss_conf.rss_key_len =3D sizeof(hashKey); > eth_config.rx_adv_conf.rss_conf.rss_hf =3D 260 > > > > With the aforementioned RSS configuration, the application is not coming > up. The same application runs without any issues on a VMware virtual > machine. > > When I set > > eth_config.rxmode.mq_mode =3D ETH_MQ_RX_NONE > eth_config.rx_adv_conf.rss_conf.rss_hf =3D 0 > > Application starts working fine. Since we need RSS support for our > application I cannot set eth_config.rxmode.mq_mode =3D ETH_MQ_RX_NONE. > > I looked at the DPDK 21.11 release notes, and it mentions that virtio_net > supports RSS support. > > > In this application traffic is tapped to capture port. I have also create= d > two queues using ACLI comments. > > vm.nic_create nutms1-ms type=3DkNetworkFunctionNic > network_function_nic_type=3DkTap queues=3D2 > > vm.nic_get testvm > xx:xx:xx:xx:xx:xx { > mac_addr: "xx:xx:xx:xx:xx:xx" > network_function_nic_type: "kTap" > network_type: "kNativeNetwork" > queues: 2 > type: "kNetworkFunctionNic" > uuid: "9c26c704-bcb3-4483-bdaf-4b64bb9233ef" > } > > > Additionally, I've turned on dpdk logging. PFB the dpdk log's output. > > EAL: PCI device 0000:00:05.0 on NUMA socket 0 > EAL: probe driver: 1af4:1000 net_virtio > EAL: Probe PCI driver: net_virtio (1af4:1000) device: 0000:00:05.0 (socke= t > 0) > EAL: PCI memory mapped at 0x940000000 > EAL: PCI memory mapped at 0x940001000 > virtio_read_caps(): [98] skipping non VNDR cap id: 11 > virtio_read_caps(): [84] cfg type: 5, bar: 0, offset: 0000, len: 0 > virtio_read_caps(): [70] cfg type: 2, bar: 4, offset: 3000, len: 4096 > virtio_read_caps(): [60] cfg type: 4, bar: 4, offset: 2000, len: 4096 > virtio_read_caps(): [50] cfg type: 3, bar: 4, offset: 1000, len: 4096 > virtio_read_caps(): [40] cfg type: 1, bar: 4, offset: 0000, len: 4096 > virtio_read_caps(): found modern virtio pci device. > virtio_read_caps(): common cfg mapped at: 0x940001000 > virtio_read_caps(): device cfg mapped at: 0x940003000 > virtio_read_caps(): isr cfg mapped at: 0x940002000 > virtio_read_caps(): notify base: 0x940004000, notify off multiplier: 4 > vtpci_init(): modern virtio pci detected. > virtio_ethdev_negotiate_features(): guest_features before negotiate =3D > 8000005f10ef8028 > virtio_ethdev_negotiate_features(): host_features before negotiate =3D > 130ffffa7 > virtio_ethdev_negotiate_features(): features after negotiate =3D 110ef802= 0 > virtio_init_device(): PORT MAC: 50:6B:8D:A9:09:62 > virtio_init_device(): link speed =3D -1, duplex =3D 1 > virtio_init_device(): config->max_virtqueue_pairs=3D2 > virtio_init_device(): config->status=3D1 > virtio_init_device(): PORT MAC: 50:6B:8D:A9:09:62 > virtio_init_queue(): setting up queue: 0 on NUMA node 0 > virtio_init_queue(): vq_size: 256 > virtio_init_queue(): vring_size: 10244, rounded_vring_size: 12288 > virtio_init_queue(): vq->vq_ring_mem: 0x7fffab000 > virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ffab000 > virtio_init_vring(): >> > modern_setup_queue(): queue 0 addresses: > modern_setup_queue(): desc_addr: 7fffab000 > modern_setup_queue(): aval_addr: 7fffac000 > modern_setup_queue(): used_addr: 7fffad000 > modern_setup_queue(): notify addr: 0x940004000 (notify offset: 0) > virtio_init_queue(): setting up queue: 1 on NUMA node 0 > virtio_init_queue(): vq_size: 256 > virtio_init_queue(): vring_size: 10244, rounded_vring_size: 12288 > virtio_init_queue(): vq->vq_ring_mem: 0x7fffa6000 > virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ffa6000 > virtio_init_vring(): >> > modern_setup_queue(): queue 1 addresses: > modern_setup_queue(): desc_addr: 7fffa6000 > modern_setup_queue(): aval_addr: 7fffa7000 > modern_setup_queue(): used_addr: 7fffa8000 > modern_setup_queue(): notify addr: 0x940004004 (notify offset: 1) > virtio_init_queue(): setting up queue: 2 on NUMA node 0 > virtio_init_queue(): vq_size: 256 > virtio_init_queue(): vring_size: 10244, rounded_vring_size: 12288 > virtio_init_queue(): vq->vq_ring_mem: 0x7fff98000 > virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ff98000 > virtio_init_vring(): >> > modern_setup_queue(): queue 2 addresses: > modern_setup_queue(): desc_addr: 7fff98000 > modern_setup_queue(): aval_addr: 7fff99000 > modern_setup_queue(): used_addr: 7fff9a000 > modern_setup_queue(): notify addr: 0x940004008 (notify offset: 2) > virtio_init_queue(): setting up queue: 3 on NUMA node 0 > virtio_init_queue(): vq_size: 256 > virtio_init_queue(): vring_size: 10244, rounded_vring_size: 12288 > virtio_init_queue(): vq->vq_ring_mem: 0x7fff93000 > virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ff93000 > virtio_init_vring(): >> > modern_setup_queue(): queue 3 addresses: > modern_setup_queue(): desc_addr: 7fff93000 > modern_setup_queue(): aval_addr: 7fff94000 > modern_setup_queue(): used_addr: 7fff95000 > modern_setup_queue(): notify addr: 0x94000400c (notify offset: 3) > virtio_init_queue(): setting up queue: 4 on NUMA node 0 > virtio_init_queue(): vq_size: 64 > virtio_init_queue(): vring_size: 4612, rounded_vring_size: 8192 > virtio_init_queue(): vq->vq_ring_mem: 0x7fff87000 > virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ff87000 > virtio_init_vring(): >> > modern_setup_queue(): queue 4 addresses: > modern_setup_queue(): desc_addr: 7fff87000 > modern_setup_queue(): aval_addr: 7fff87400 > modern_setup_queue(): used_addr: 7fff88000 > modern_setup_queue(): notify addr: 0x940004010 (notify offset: 4) > eth_virtio_pci_init(): port 0 vendorID=3D0x1af4 deviceID=3D0x1000 > EAL: Module /sys/module/vfio not found! error 2 (No such file or director= y) > EAL: lib.telemetry log level changed from disabled to debug > TELEMETRY: Attempting socket bind to path > '/var/run/dpdk/rte/dpdk_telemetry.v2' > TELEMETRY: Initial bind to socket '/var/run/dpdk/rte/dpdk_telemetry.v2' > failed. > TELEMETRY: Attempting unlink and retrying bind > TELEMETRY: Socket creation and binding ok > TELEMETRY: Telemetry initialized ok > TELEMETRY: No legacy callbacks, legacy socket not created > [Wed Jul 26 04:44:42 2023][ms_dpi: 28098] DPDK Initialised > [Wed Jul 26 04:44:42 2023][ms_dpi: 28098] Finished DPDK logging session > > > The following result is produced when testpmd runs the RSS configuration > command. > > testpmd> port config all rss all > Port 0 modified RSS hash function based on hardware > support,requested:0x17f83fffc configured:0 > Multi-queue RSS mode isn't enabled. > Configuration of RSS hash at ethernet port 0 failed with error (95): > Operation not supported. > > > Any suggestions on how to enable RSS support in this situation would be > greatly appreciated. > > Thank you for your assistance. > --00000000000025b23006015eda0c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks=C2=A0Bing for quick response.

Th= e virtio driver version 1.0.0 is included in the Linux kernel version 4.9 t= hat powers VM.

ethtool -i eth1
driver: virtio_net
version: 1.0= .0
firmware-version:
expansion-rom-version:
bus-info: 0000:00:04.0=

Nutanix document stats that "Ensure the AHV UVM is running the= latest Nutanix VirtIO driver package. Nutanix VirtIO 1.1.6 or higher is re= quired for RSS support. " Linux kernel version: 5.4 and later will hav= e Virtio 1.1.6.

Since the programme is built on the dpdk, the PMD dr= iver will use the eth interface rather than the one that the kernel provide= s. I apologise if I'm mistaken. RSS is supported by the dpdk PMD versio= n in use.

Because of the client-centric nature of this application,= upgrading the kernel will be challenging.

Do you believe that the = only option is to upgrade the vm kernel version?

T= hanks ,
Shiv=C2=A0

=
On Wed, Jul 26, 2023 at 12:33=E2=80= =AFPM Bing Zhao <bingz@nvidia.com> wrote:

IIRC, the =E2=80=9CVIRTIO_NET_F_RSS=E2=80=9D is some= capability reported and decided during the driver setup/communication stag= e. It is mostly like that your libs/drivers running on the host for the VM = does not support this feature.

Have you tried to update the versions of VM or the p= ackage/lib of VirtIO for this VM?

=C2=A0

From: shiv chittora <shiv.chittora@gmail.com> Sent: Wednesday, July 26, 2023 1:05 PM
To: users@dpdk.o= rg
Subject: Enable RSS for virtio application ( dpdk version 21.11)<= /u>

=C2=A0

External email: Use caution opening links or atta= chments

=C2=A0

I'm using a Nutanix virtual machine to run a DPD= K(Version 21.11)-based application.
Application is failing during rte_eth_dev_configure . For our application, = RSS support is required.

eth_config.rxmode.mq_mode =3D ETH_MQ_RX_RSS;
static uint8_t hashKey[] =3D {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5= A, 0x6D, 0x5A,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5= A, 0x6D, 0x5A,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5= A, 0x6D, 0x5A,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5= A, 0x6D, 0x5A,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5= A, 0x6D, 0x5A,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 };

=C2=A0 =C2=A0 =C2=A0 =C2=A0 eth_config.rx_adv_conf.rss_conf.rss_key =3D has= hKey;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 eth_config.rx_adv_conf.rss_conf.rss_key_len =3D= sizeof(hashKey);
eth_config.rx_adv_conf.rss_conf.rss_hf =3D 260



With the aforementioned RSS configuration, the application is not coming up= . The same application runs without any issues on a VMware virtual machine.= =C2=A0

When I set

=C2=A0 =C2=A0 eth_config.rxmode.mq_mode =3D ETH_MQ_RX_NONE
eth_config.rx_adv_conf.rss_conf.rss_hf =3D 0

Application starts working fine. Since we need RSS support for our applicat= ion I cannot set eth_config.rxmode.mq_mode =3D ETH_MQ_RX_NONE.

I looked at the DPDK 21.11 release notes, and it mentions that virtio_net s= upports RSS support.


In this application traffic is tapped to capture port. I have also created = two queues using ACLI comments. =C2=A0

<acropolis> vm.nic_create nutms1-ms type=3DkNetworkFunctionNic networ= k_function_nic_type=3DkTap queues=3D2

<acropolis> vm.nic_get testvm
xx:xx:xx:xx:xx:xx {
=C2=A0 mac_addr: "xx:xx:xx:xx:xx:xx"
=C2=A0 network_function_nic_type: "kTap"
=C2=A0 network_type: "kNativeNetwork"
=C2=A0 queues: 2
=C2=A0 type: "kNetworkFunctionNic"
=C2=A0 uuid: "9c26c704-bcb3-4483-bdaf-4b64bb9233ef"
}


Additionally, I've turned on dpdk logging. PFB the dpdk log's outpu= t.

EAL: PCI device 0000:00:05.0 on NUMA socket 0
EAL: =C2=A0 probe driver: 1af4:1000 net_virtio
EAL: Probe PCI driver: net_virtio (1af4:1000) device: 0000:00:05.0 (socket = 0)
EAL: =C2=A0 PCI memory mapped at 0x940000000
EAL: =C2=A0 PCI memory mapped at 0x940001000
virtio_read_caps(): [98] skipping non VNDR cap id: 11
virtio_read_caps(): [84] cfg type: 5, bar: 0, offset: 0000, len: 0
virtio_read_caps(): [70] cfg type: 2, bar: 4, offset: 3000, len: 4096
virtio_read_caps(): [60] cfg type: 4, bar: 4, offset: 2000, len: 4096
virtio_read_caps(): [50] cfg type: 3, bar: 4, offset: 1000, len: 4096
virtio_read_caps(): [40] cfg type: 1, bar: 4, offset: 0000, len: 4096
virtio_read_caps(): found modern virtio pci device.
virtio_read_caps(): common cfg mapped at: 0x940001000
virtio_read_caps(): device cfg mapped at: 0x940003000
virtio_read_caps(): isr cfg mapped at: 0x940002000
virtio_read_caps(): notify base: 0x940004000, notify off multiplier: 4
vtpci_init(): modern virtio pci detected.
virtio_ethdev_negotiate_features(): guest_features before negotiate =3D 800= 0005f10ef8028
virtio_ethdev_negotiate_features(): host_features before negotiate =3D 130f= fffa7
virtio_ethdev_negotiate_features(): features after negotiate =3D 110ef8020<= br> virtio_init_device(): PORT MAC: 50:6B:8D:A9:09:62
virtio_init_device(): link speed =3D -1, duplex =3D 1
virtio_init_device(): config->max_virtqueue_pairs=3D2
virtio_init_device(): config->status=3D1
virtio_init_device(): PORT MAC: 50:6B:8D:A9:09:62
virtio_init_queue(): setting up queue: 0 on NUMA node 0
virtio_init_queue(): vq_size: 256
virtio_init_queue(): vring_size: 10244, rounded_vring_size: 12288
virtio_init_queue(): vq->vq_ring_mem: 0x7fffab000
virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ffab000
virtio_init_vring(): =C2=A0>>
modern_setup_queue(): queue 0 addresses:
modern_setup_queue(): =C2=A0 =C2=A0desc_addr: 7fffab000
modern_setup_queue(): =C2=A0 =C2=A0aval_addr: 7fffac000
modern_setup_queue(): =C2=A0 =C2=A0used_addr: 7fffad000
modern_setup_queue(): =C2=A0 =C2=A0notify addr: 0x940004000 (notify offset:= 0)
virtio_init_queue(): setting up queue: 1 on NUMA node 0
virtio_init_queue(): vq_size: 256
virtio_init_queue(): vring_size: 10244, rounded_vring_size: 12288
virtio_init_queue(): vq->vq_ring_mem: 0x7fffa6000
virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ffa6000
virtio_init_vring(): =C2=A0>>
modern_setup_queue(): queue 1 addresses:
modern_setup_queue(): =C2=A0 =C2=A0desc_addr: 7fffa6000
modern_setup_queue(): =C2=A0 =C2=A0aval_addr: 7fffa7000
modern_setup_queue(): =C2=A0 =C2=A0used_addr: 7fffa8000
modern_setup_queue(): =C2=A0 =C2=A0notify addr: 0x940004004 (notify offset:= 1)
virtio_init_queue(): setting up queue: 2 on NUMA node 0
virtio_init_queue(): vq_size: 256
virtio_init_queue(): vring_size: 10244, rounded_vring_size: 12288
virtio_init_queue(): vq->vq_ring_mem: 0x7fff98000
virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ff98000
virtio_init_vring(): =C2=A0>>
modern_setup_queue(): queue 2 addresses:
modern_setup_queue(): =C2=A0 =C2=A0desc_addr: 7fff98000
modern_setup_queue(): =C2=A0 =C2=A0aval_addr: 7fff99000
modern_setup_queue(): =C2=A0 =C2=A0used_addr: 7fff9a000
modern_setup_queue(): =C2=A0 =C2=A0notify addr: 0x940004008 (notify offset:= 2)
virtio_init_queue(): setting up queue: 3 on NUMA node 0
virtio_init_queue(): vq_size: 256
virtio_init_queue(): vring_size: 10244, rounded_vring_size: 12288
virtio_init_queue(): vq->vq_ring_mem: 0x7fff93000
virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ff93000
virtio_init_vring(): =C2=A0>>
modern_setup_queue(): queue 3 addresses:
modern_setup_queue(): =C2=A0 =C2=A0desc_addr: 7fff93000
modern_setup_queue(): =C2=A0 =C2=A0aval_addr: 7fff94000
modern_setup_queue(): =C2=A0 =C2=A0used_addr: 7fff95000
modern_setup_queue(): =C2=A0 =C2=A0notify addr: 0x94000400c (notify offset:= 3)
virtio_init_queue(): setting up queue: 4 on NUMA node 0
virtio_init_queue(): vq_size: 64
virtio_init_queue(): vring_size: 4612, rounded_vring_size: 8192
virtio_init_queue(): vq->vq_ring_mem: 0x7fff87000
virtio_init_queue(): vq->vq_ring_virt_mem: 0x17ff87000
virtio_init_vring(): =C2=A0>>
modern_setup_queue(): queue 4 addresses:
modern_setup_queue(): =C2=A0 =C2=A0desc_addr: 7fff87000
modern_setup_queue(): =C2=A0 =C2=A0aval_addr: 7fff87400
modern_setup_queue(): =C2=A0 =C2=A0used_addr: 7fff88000
modern_setup_queue(): =C2=A0 =C2=A0notify addr: 0x940004010 (notify offset:= 4)
eth_virtio_pci_init(): port 0 vendorID=3D0x1af4 deviceID=3D0x1000
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)=
EAL: lib.telemetry log level changed from disabled to debug
TELEMETRY: Attempting socket bind to path '/var/run/dpdk/rte/dpdk_telem= etry.v2'
TELEMETRY: Initial bind to socket '/var/run/dpdk/rte/dpdk_telemetry.v2&= #39; failed.
TELEMETRY: Attempting unlink and retrying bind
TELEMETRY: Socket creation and binding ok
TELEMETRY: Telemetry initialized ok
TELEMETRY: No legacy callbacks, legacy socket not created
[Wed Jul 26 04:44:42 2023][ms_dpi: 28098] DPDK Initialised
[Wed Jul 26 04:44:42 2023][ms_dpi: 28098] Finished DPDK logging session


The following result is produced when testpmd runs the RSS configuration co= mmand.

testpmd> port config all rss all
Port 0 modified RSS hash function based on hardware support,requested:0x17f= 83fffc configured:0
Multi-queue RSS mode isn't enabled.
Configuration of RSS hash at ethernet port 0 failed with error (95): Operat= ion not supported.


Any suggestions on how to enable RSS support in this situation would be gre= atly appreciated.

Thank you for your assistance.=C2=A0

--00000000000025b23006015eda0c--