DPDK usage discussions
 help / color / mirror / Atom feed
From: Long Li <longli@microsoft.com>
To: Tyler Blair <tblair@fastmail.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] qdisc errors on 20.11.1 & Azure
Date: Wed, 7 Jul 2021 16:05:55 +0000	[thread overview]
Message-ID: <BY5PR21MB1506AC6E5CFA6C001FFC1F62CE1A9@BY5PR21MB1506.namprd21.prod.outlook.com> (raw)
In-Reply-To: <0c3b2d55-6e9e-43bd-bf33-b734f8b17d44@www.fastmail.com>

Hi Tyler,

Nvidia helped investigate this.

The message "Failed to allocate Tx DevX UAR (BF)" is diagnostic, not error.
We lowered the log level for this to DEBUG in 21.02. If the further UAR allocation with NC mapping succeeds - there is no known issues about PMD operating.
(if both BF/NC fail - no device probing happens, as we saw).
Hence - just ignore the diagnostic message or use 21.05 or apply the commit " net/mlx5: fix UAR allocation diagnostics messages".

Thanks,
Long


> -----Original Message-----
> From: Tyler Blair <tblair@fastmail.com>
> Sent: Tuesday, July 6, 2021 9:11 AM
> To: Stephen Hemminger <stephen@networkplumber.org>
> Cc: users@dpdk.org; Long Li <longli@microsoft.com>
> Subject: Re: [dpdk-users] qdisc errors on 20.11.1 & Azure
> 
> > The next thing to check is version of rdma-core. Long just diagnosed
> > an issue with rdma-core version in Ubuntu 20.4
> 
> That's the version I'm using in my last reply -- from ppa:canonical-
> server/server-backports: 33.1-1ubuntu1~backport20.04-
> 202103240925~ubuntu20.04.1
> 
> Noticed now, but with the new kernal and rdma-core librdmacm-dev from
> backports there are some new mlx5_pci errors. Appears to be working OK
> otherwise though.
> 
> EAL: Detected 8 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Detected static linkage of DPDK
> EAL: Selected IOVA mode 'VA'
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: Probe PCI driver: mlx5_pci (15b3:1016) device: 5ed7:00:02.0 (socket 0)
> ** mlx5_pci: Failed to allocate Tx DevX UAR (BF)
> ** mlx5_pci: Failed to allocate Rx DevX UAR (BF)
> ** mlx5_pci: No available register for Sampler.
> ** mlx5_pci: Size 0xFFFF is not power of 2, will be aligned to 0x10000.
> net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3)
> tap_nl_dump_ext_ack(): Cannot delete qdisc with handle of zero
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> Warning: NUMA should be configured manually by using --port-numa-config
> and --ring-numa-config parameters along with --numa.
> 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 1 (socket 0)
> Port 1: 00:22:48:3B:AB:CC
> Checking link statuses...
> 
> Marked with ** - these appear to be pretty benign as well though.
> 
> Regards,
> Tyler

  reply	other threads:[~2021-07-07 16:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 11:36 Tyler Blair
2021-06-29 17:43 ` Stephen Hemminger
2021-07-05 11:05   ` Tyler Blair
2021-07-05 16:24     ` Stephen Hemminger
2021-07-06 14:35       ` Tyler Blair
2021-07-06 14:57         ` Stephen Hemminger
2021-07-06 16:10           ` Tyler Blair
2021-07-07 16:05             ` Long Li [this message]
2021-07-13 12:56               ` Tyler Blair

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=BY5PR21MB1506AC6E5CFA6C001FFC1F62CE1A9@BY5PR21MB1506.namprd21.prod.outlook.com \
    --to=longli@microsoft.com \
    --cc=stephen@networkplumber.org \
    --cc=tblair@fastmail.com \
    --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).