From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix Tx queues creation type check for scheduling
Date: Thu, 29 Jul 2021 15:16:45 +0000 [thread overview]
Message-ID: <DM4PR12MB50543921231E556A841BEE10CFEB9@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210729122643.24865-1-viacheslavo@nvidia.com>
Hi,
> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Thursday, July 29, 2021 3:27 PM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; stable@dpdk.org
> Subject: [PATCH] net/mlx5: fix Tx queues creation type check for scheduling
>
> The send scheduling on timestamp offload requires the Send
> Queue (SQ) shares its User Access Region (UAR) with the
> pacing Clock Queue. The SQ can be created by mlx5 PMD either
> with DevX or with Verbs. If the SQ is being created with
> DevX the dedicated UAR can be specified and all the SQs
> share the single UAR. Once SQ is being created with Verbs
> the SQ's UAR is allocated by the rdma-core library internally
> on its own and there are no UAR sharing. This caused hardware
> errors on WAIT WQEs and overall send scheduling malfunction.
>
> If SQs are going to be created with Verbs and the send
> scheduling offload is explicitly requested via tx_pp devarg
> the device probing is rejected as device configuration
> can't satisfy the requirements.
>
> Fixes: 3ec73abeed52 ("net/mlx5/linux: fix Tx queue operations decision")
> Fixes: 8f848f32fc24 ("net/mlx5: introduce send scheduling devargs")
> Cc: stable@dpdk.org
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2021-07-29 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 12:26 Viacheslav Ovsiienko
2021-07-29 15:16 ` Raslan Darawsheh [this message]
2021-07-29 17:39 ` Thomas Monjalon
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=DM4PR12MB50543921231E556A841BEE10CFEB9@DM4PR12MB5054.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).