From: Ori Kam <orika@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>,
Raslan Darawsheh <rasland@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Dekel Peled <dekelp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix UAR memory mapping type
Date: Thu, 23 Jul 2020 11:58:29 +0000 [thread overview]
Message-ID: <AM6PR05MB5176F07D86EEAD43EE60DB0BDB760@AM6PR05MB5176.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1595429948-20873-1-git-send-email-viacheslavo@mellanox.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Viacheslav Ovsiienko
>
> The User Access Region is a special mechanism to provide direct
> access to the hardware registers, and is the part of PCI address
> space that is mapped to CPU virtual address. The mapping can be
> performed with the type "Write-Combining" or "Non-Cached", and
> these ones might be supported or not on different setups.
>
> To prevent device probing failure the UAR allocation attempt
> with alternative mapping type is performed. The datapath
> takes the actual UAR mapping into account on queue creation.
>
> There was another issue with NULL UAR base address.
> OFED 5.0.x and Upstream rdma_core before v29 returned the NULL as
> UAR base address if UAR was not the first object in the UAR page.
> It caused the PMD failure and we should try to get another UAR
> till we get the first one with non-NULL base address returned.
>
> Fixes: fc4d4f732bbc ("net/mlx5: introduce shared UAR resource")
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> --
> 1.8.3.1
Acked-by: Ori Kam <orika@mellanox.com>
Thanks,
Ori
next prev parent reply other threads:[~2020-07-23 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 14:59 Viacheslav Ovsiienko
2020-07-23 11:58 ` Ori Kam [this message]
2020-07-23 12:34 ` Raslan Darawsheh
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=AM6PR05MB5176F07D86EEAD43EE60DB0BDB760@AM6PR05MB5176.eurprd05.prod.outlook.com \
--to=orika@mellanox.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=rasland@mellanox.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@mellanox.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).