From: Kevin Traynor <ktraynor@redhat.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, stable@dpdk.org
Cc: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH 21.11] common/mlx5: fix error CQE handling for 128 bytes CQE
Date: Tue, 3 Dec 2024 17:54:54 +0000 [thread overview]
Message-ID: <d0c24630-1dda-423a-8ce2-cb427ea40889@redhat.com> (raw)
In-Reply-To: <4c30bab5-9f6f-4b68-a569-ab3e34cd27ad@redhat.com>
On 03/12/2024 18:43, Kevin Traynor wrote:
> On 27/11/2024 18:48, Alexander Kozyrev wrote:
>> [ upstream commit 3cddeba0ca38b00c7dc646277484d08a4cb2d862 ]
>>
>> The completion queue element size can be independently configured
>> to report either 64 or 128 bytes CQEs by programming cqe_sz parameter
>> at CQ creation. This parameter depends on the cache line size and
>> affects both regular CQEs and error CQEs. But the error handling
>> assumes that an error CQE is 64 bytes and doesn't take the padding
>> into consideration on platforms with 128-byte cache lines.
>> Fix the error CQE size in all error handling routines in mlx5.
>>
> Hi Alexander,
>
> This is causing a build error [1] on windows in the crypto code [2].
>
> ref
> https://dpdkdashboard.iol.unh.edu/results/dashboard/testruns/logs/1475543/
>
> I didn't spend time to analyse. If you have a fix I can apply, or else
> we can drop the patch.
>
> thanks,
> Kevin.
>
> [1]
> ../drivers/crypto/mlx5/mlx5_crypto.c
> ../drivers/crypto/mlx5/mlx5_crypto.c:480:52: error: incomplete
> definition of type 'struct mlx5_err_cqe'
> DRV_LOG(ERR, "CQE ERR:%x.\n", rte_be_to_cpu_32(cqe->syndrome));
> ~~~^
> [2]
> mlx5_crypto_cqe_err_handle(struct mlx5_crypto_qp *qp, struct
> rte_crypto_op *op)
> {
> const uint32_t idx = qp->ci & (qp->entries_n - 1);
> volatile struct mlx5_err_cqe *cqe = (volatile struct mlx5_err_cqe *)
> &qp->cq_obj.cqes[idx];
>
> op->status = RTE_CRYPTO_OP_STATUS_ERROR;
> qp->stats.dequeue_err_count++;
> DRV_LOG(ERR, "CQE ERR:%x.\n", rte_be_to_cpu_32(cqe->syndrome));
> }
>
btw, the code that was run is ahead of the 21.11 branch.
It is at: https://dpdk.org/git/dpdk-stable on branch 21.11-staging
next prev parent reply other threads:[~2024-12-03 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 17:48 Alexander Kozyrev
2024-12-03 17:43 ` Kevin Traynor
2024-12-03 17:54 ` Kevin Traynor [this message]
2024-12-03 18:08 ` Alexander Kozyrev
2024-12-03 18:17 ` Kevin Traynor
2024-12-04 11:33 ` Kevin Traynor
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=d0c24630-1dda-423a-8ce2-cb427ea40889@redhat.com \
--to=ktraynor@redhat.com \
--cc=akozyrev@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).