DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Saoirse O'Donovan <saoirse.odonovan@intel.com>,
	Kai Ji <kai.ji@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, piotrx.bronowski@intel.com, stable@dpdk.org,
	"Xueming(Steven) Li" <xuemingl@nvidia.com>
Subject: Re: [PATCH v2] crypto/ipsec_mb: enqueue counter fix
Date: Thu, 20 Apr 2023 11:49:37 +0100	[thread overview]
Message-ID: <f7085b9e-3fa2-5af6-10ed-24c47a9e33ad@redhat.com> (raw)
In-Reply-To: <20230420103141.8770-1-saoirse.odonovan@intel.com>

On 20/04/2023 11:31, Saoirse O'Donovan wrote:
> This patch removes enqueue op counter update from the process_op_bit
> function where the process is now done in dequeue stage. The original
> stats increment was incorrect as they shouldn't have been updated at all
> in this function.
> 
> Fixes: 4f1cfda59ad3 ("crypto/ipsec_mb: move snow3g PMD")
> Cc: piotrx.bronowski@intel.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Saoirse O'Donovan <saoirse.odonovan@intel.com>
> 
> ---
> v2: Added cc stable for 21.11 and 22.11 backport.
> 
> A similar fix has been sent to 20.11 LTS stable, in the interest of
> time. In that fix, the enqueued stat is still in use, therefore only the
> fix to the count increment was necessary.
> 

Thanks for the explanation. As it has the correct tags, we will pick 
this up for 21.11 and 22.11 LTS releases in the normal workflow, which 
is after it has been released as part of a DPDK main branch release.

thanks,
Kevin.

> Here is the mail archive link:
> https://mails.dpdk.org/archives/stable/2023-April/043550.html
> ---
>   drivers/crypto/ipsec_mb/pmd_snow3g.c | 16 ++++++++--------
>   1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/crypto/ipsec_mb/pmd_snow3g.c b/drivers/crypto/ipsec_mb/pmd_snow3g.c
> index 8ed069f428..e64df1a462 100644
> --- a/drivers/crypto/ipsec_mb/pmd_snow3g.c
> +++ b/drivers/crypto/ipsec_mb/pmd_snow3g.c
> @@ -372,9 +372,10 @@ process_ops(struct rte_crypto_op **ops, struct snow3g_session *session,
>   /** Process a crypto op with length/offset in bits. */
>   static int
>   process_op_bit(struct rte_crypto_op *op, struct snow3g_session *session,
> -		struct ipsec_mb_qp *qp, uint16_t *accumulated_enqueued_ops)
> +		struct ipsec_mb_qp *qp)
>   {
> -	uint32_t enqueued_op, processed_op;
> +	unsigned int processed_op;
> +	int ret;
>   
>   	switch (session->op) {
>   	case IPSEC_MB_OP_ENCRYPT_ONLY:
> @@ -421,9 +422,10 @@ process_op_bit(struct rte_crypto_op *op, struct snow3g_session *session,
>   
>   	if (unlikely(processed_op != 1))
>   		return 0;
> -	enqueued_op = rte_ring_enqueue(qp->ingress_queue, op);
> -	qp->stats.enqueued_count += enqueued_op;
> -	*accumulated_enqueued_ops += enqueued_op;
> +
> +	ret = rte_ring_enqueue(qp->ingress_queue, op);
> +	if (ret != 0)
> +		return ret;
>   
>   	return 1;
>   }
> @@ -439,7 +441,6 @@ snow3g_pmd_dequeue_burst(void *queue_pair,
>   	struct snow3g_session *prev_sess = NULL, *curr_sess = NULL;
>   	uint32_t i;
>   	uint8_t burst_size = 0;
> -	uint16_t enqueued_ops = 0;
>   	uint8_t processed_ops;
>   	uint32_t nb_dequeued;
>   
> @@ -479,8 +480,7 @@ snow3g_pmd_dequeue_burst(void *queue_pair,
>   				prev_sess = NULL;
>   			}
>   
> -			processed_ops = process_op_bit(curr_c_op, curr_sess,
> -							qp, &enqueued_ops);
> +			processed_ops = process_op_bit(curr_c_op, curr_sess, qp);
>   			if (processed_ops != 1)
>   				break;
>   


  reply	other threads:[~2023-04-20 10:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 14:22 [PATCH] " Saoirse O'Donovan
2023-04-18 14:26 ` Power, Ciara
2023-04-20 10:31 ` [PATCH v2] " Saoirse O'Donovan
2023-04-20 10:49   ` Kevin Traynor [this message]
2023-04-20 11:05   ` Power, Ciara
2023-05-24 12:22   ` [EXT] " Akhil Goyal

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=f7085b9e-3fa2-5af6-10ed-24c47a9e33ad@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=piotrx.bronowski@intel.com \
    --cc=saoirse.odonovan@intel.com \
    --cc=stable@dpdk.org \
    --cc=xuemingl@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).