patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Tal Shnaiderman <talshn@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"matan@nvidia.com" <matan@nvidia.com>,
	"rasland@nvidia.com" <rasland@nvidia.com>,
	"asafp@nvidia.com" <asafp@nvidia.com>,
	"suanmingm@nvidia.com" <suanmingm@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [EXT] [dpdk-dev] [PATCH] crypto/mlx5: fix crypto QP indexing
Date: Fri, 24 Sep 2021 17:47:22 +0000	[thread overview]
Message-ID: <CO6PR18MB44842AB28188E8D453B276F6D8A49@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210913140224.18788-1-talshn@nvidia.com>

> The crypto QP consumer (ci) and producer (pi) indexes are increased
> with each successful enqueue/dequeue operations.
> 
> However the QP pi index is calculated with a wraparound the number
> of elements while the QP ci does not.
> 
> This is causing incorrect engine calculation for encqueued WQ values
> (wq->pi - wq->ci) and eventually the device stops accepting new enqueue
> operations.
> 
> Fixed by removing the wraparound on QP pi and using a temp calculation
> where wraparound values are needed.
> 
> Fixes: 8e196c08ab53 ("crypto/mlx5: support enqueue/dequeue operations")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
Applied to dpdk-next-crypto


      reply	other threads:[~2021-09-24 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 14:02 [dpdk-stable] " Tal Shnaiderman
2021-09-24 17:47 ` Akhil Goyal [this message]

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=CO6PR18MB44842AB28188E8D453B276F6D8A49@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=asafp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=talshn@nvidia.com \
    --cc=thomas@monjalon.net \
    /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).