From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Alessandro Pagani <alessandropagani.90@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>, Asaf Penso <asafp@nvidia.com>
Subject: Re: [dpdk-users] DPDK 20.11 MLX5 testpmd tx_pp 'WQE index ignore feature is required for packet pacing'
Date: Fri, 11 Dec 2020 16:19:58 +0000 [thread overview]
Message-ID: <MWHPR12MB15018B03FDED667573C0C581DFCA0@MWHPR12MB1501.namprd12.prod.outlook.com> (raw)
In-Reply-To: <5238000.dFEpQ3j31A@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, December 11, 2020 17:48
> To: Alessandro Pagani <alessandropagani.90@gmail.com>
> Cc: users@dpdk.org; Slava Ovsiienko <viacheslavo@nvidia.com>; Asaf Penso
> <asafp@nvidia.com>
> Subject: Re: [dpdk-users] DPDK 20.11 MLX5 testpmd tx_pp 'WQE index ignore
> feature is required for packet pacing'
>
> 09/12/2020 17:03, Alessandro Pagani:
> > Hi all,
> >
> > I am trying to run dpdk testpmd with Mellanox ConnectX4 Lx (mlx5 driver).
> >
> > I am specifying the tx_pp parameter to provide the packet send
> > scheduling on mbuf timestamps, but the testpmd fails with the following
> error:
> [...]
> > EAL: Probe PCI driver: mlx5_pci (15b3:1015) device: 0000:3b:00.0
This is ConnectX-4LX (DevID is 1015), it does not support scheduling.
Tx scheduling is supported since ConnectX-6DX.
> > (socket 0)
> > mlx5_pci: No available register for Sampler.
> > mlx5_pci: WQE index ignore feature is required for packet pacing
> > mlx5_pci: probe of PCI device 0000:3b:00.0 aborted after encountering
> > an
> > error: No such device
> > common_mlx5: Failed to load driver = mlx5_pci.
> >
> > EAL: Requested device 0000:3b:00.0 cannot be used
> [...]
> > The error messages suggest that "WQE index ignore feature is required
> > for packet pacing".
> >
> > Anyone knows the reason of this error and how to solve it?
>
> I think it means your device does not support this feature.
> But I realize it is not documented here:
Yes, indeed. I'll provide the patch, thank you for noticing that.
With best regards, Slava
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dp
> dk.org%2Fguides%2Fnics%2Fmlx5.html%23supported-hardware-
> offloads&data=04%7C01%7Cviacheslavo%40nvidia.com%7C68077a428d9
> 140ecac4408d89dec2c93%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0
> %7C637432984987268866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA
> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sda
> ta=2n5MI7WLln9xRPcpQzSy2Q2g3xPlYnYrK6YIeRKxS9Q%3D&reserved=0
>
>
next prev parent reply other threads:[~2020-12-11 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 16:03 Alessandro Pagani
2020-12-11 15:48 ` Thomas Monjalon
2020-12-11 16:19 ` Slava Ovsiienko [this message]
2020-12-11 16:31 ` Thomas Monjalon
2020-12-11 16:44 ` Slava Ovsiienko
2020-12-16 6:40 ` Alessandro Pagani
2020-12-13 10:29 ` 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=MWHPR12MB15018B03FDED667573C0C581DFCA0@MWHPR12MB1501.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=alessandropagani.90@gmail.com \
--cc=asafp@nvidia.com \
--cc=thomas@monjalon.net \
--cc=users@dpdk.org \
/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).