DPDK usage discussions
 help / color / mirror / Atom feed
From: Asaf Penso <asafp@nvidia.com>
To: Haider Ali <haider@dreambigsemi.com>,
	Muhammad Zain-ul-Abideen <zain2294@gmail.com>
Cc: users <users@dpdk.org>
Subject: RE: Mellanox VF failed to start with hairpin queues
Date: Tue, 22 Feb 2022 17:56:46 +0000	[thread overview]
Message-ID: <DM5PR1201MB2555E6D76CED7E76EF827989CD3B9@DM5PR1201MB2555.namprd12.prod.outlook.com> (raw)
In-Reply-To: <MWHPR2201MB10559D70EBBAFAA1B3D7452DA72C9@MWHPR2201MB1055.namprd22.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

I worked with Haider and found that the VF should be configured as trusted both in driver and FW.
I am working on a documentation patch in mlx5.rst to describe the needed steps.

Regards,
Asaf Penso

From: Haider Ali <haider@dreambigsemi.com>
Sent: Monday, February 7, 2022 3:12 PM
To: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: Mellanox VF failed to start with hairpin queues

I am not using mlx5 VF in VM. Can you please elaborate on what type of setup information you require?

Regards,
Haider Ali
________________________________
From: Muhammad Zain-ul-Abideen <zain2294@gmail.com<mailto:zain2294@gmail.com>>
Sent: Friday, February 4, 2022 5:23 PM
To: Haider Ali <haider@dreambigsemi.com<mailto:haider@dreambigsemi.com>>
Cc: users <users@dpdk.org<mailto:users@dpdk.org>>
Subject: Re: Mellanox VF failed to start with hairpin queues

You don't often get email from zain2294@gmail.com<mailto:zain2294@gmail.com>. Learn why this is important<http://aka.ms/LearnAboutSenderIdentification>
Haider, have u installed mlx5 drivers in vm server? What setup u r using. A little more detail will help

On Fri, Feb 4, 2022, 1:06 PM Haider Ali <haider@dreambigsemi.com<mailto:haider@dreambigsemi.com>> wrote:
Hi,

Can anyone please guide me on why I am not able to do hairpin on VF? I am running the testpmd application with 1 Hairpin queue and 1 standard queue pair on Mellanox VF but getting following error:

$ sudo ./build/app/dpdk-testpmd -l 1,3 -n 4 -a 04:01.2 -- -i --rxq=1 --txq=1 --hairpinq=1 --hairpin-mode=0x00

EAL: Probe PCI driver: mlx5_pci (15b3:101e) device: 0000:04:01.2 (socket 0)
TELEMETRY: No legacy callbacks, legacy socket not created
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_1>: n=155456, size=2176, socket=1
testpmd: preferred mempool ops selected: ring_mp_mc
testpmd: create a new mbuf pool <mb_pool_0>: n=155456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc

Warning! port-topology=paired and odd forward ports number, the last port will pair with itself.

Configuring Port 0 (socket 0)
mlx5_net: port 0 failed to set defaults flows
Fail to start port 0: Operation not supported
Please stop the ports first
Done
testpmd> quit

Regards,
Haider Ali

[-- Attachment #2: Type: text/html, Size: 9702 bytes --]

  reply	other threads:[~2022-02-22 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 12:31 Haider Ali
2022-02-04 12:23 ` Muhammad Zain-ul-Abideen
2022-02-07 13:12   ` Haider Ali
2022-02-22 17:56     ` Asaf Penso [this message]
2022-02-28  8:14       ` Asaf Penso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM5PR1201MB2555E6D76CED7E76EF827989CD3B9@DM5PR1201MB2555.namprd12.prod.outlook.com \
    --to=asafp@nvidia.com \
    --cc=haider@dreambigsemi.com \
    --cc=users@dpdk.org \
    --cc=zain2294@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).