From: Akhil Goyal <gakhil@marvell.com>
To: Radu Nicolau <radu.nicolau@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"ciara.power@intel.com" <ciara.power@intel.com>,
"ting-kai.ku@intel.com" <ting-kai.ku@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Volodymyr Fialko <vfialko@marvell.com>
Subject: RE: [EXT] [PATCH] examples/ipsec-secgw: fix cryptodev to SA mapping
Date: Thu, 22 Feb 2024 17:35:20 +0000 [thread overview]
Message-ID: <CO6PR18MB4484D7BCE6BF94E8BD8F8934D8562@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20231211095349.9895-1-radu.nicolau@intel.com>
> @@ -908,7 +907,11 @@ ipsec_enqueue(ipsec_xform_fn xform_func, struct
> ipsec_ctx *ipsec_ctx,
> continue;
> }
>
> - enqueue_cop(sa->cqp[ipsec_ctx->lcore_id], &priv->cop);
> + if (sa->cqp[ipsec_ctx->lcore_id])
> + enqueue_cop(sa->cqp[ipsec_ctx->lcore_id], &priv->cop);
> + else
> + RTE_LOG(ERR, IPSEC, "No CQP available for lcore %d\n",
> + ipsec_ctx->lcore_id);
Can we add likely here?
next prev parent reply other threads:[~2024-02-22 17:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 9:53 Radu Nicolau
2023-12-12 1:36 ` Ku, Ting-Kai
2024-01-22 13:21 ` Power, Ciara
2024-01-22 13:52 ` Ji, Kai
2024-02-22 17:35 ` Akhil Goyal [this message]
2024-02-23 11:01 ` [PATCH v2] " Radu Nicolau
2024-02-26 4:48 ` [EXT] " Anoob Joseph
2024-02-26 10:25 ` [PATCH v3] " Radu Nicolau
2024-02-26 23:02 ` Patrick Robb
2024-02-27 5:19 ` [EXT] " Anoob Joseph
2024-02-27 10:10 ` Radu Nicolau
2024-02-27 11:22 ` Anoob Joseph
2024-02-27 13:28 ` [PATCH v4] " Radu Nicolau
2024-02-27 13:50 ` [EXT] " Anoob Joseph
2024-03-13 14:26 ` 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=CO6PR18MB4484D7BCE6BF94E8BD8F8934D8562@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=radu.nicolau@intel.com \
--cc=stable@dpdk.org \
--cc=ting-kai.ku@intel.com \
--cc=vfialko@marvell.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).