From: jhascoet <ju.hascoet@gmail.com>
To: dev@dpdk.org
Cc: jhascoet <jhascoet@kalrayinc.com>,
stable@dpdk.org, Kai Ji <kai.ji@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
David Coyle <david.coyle@intel.com>,
"Kevin O'Sullivan" <kevin.osullivan@intel.com>,
Ciara Power <ciara.power@intel.com>
Subject: [PATCH] driver: crypto: scheduler: fix session size computation
Date: Tue, 2 Jul 2024 09:50:52 +0200 [thread overview]
Message-ID: <20240702075052.1697714-1-jhascoet@kalrayinc.com> (raw)
The crypto scheduler session size computation was taking
into account only the worker session sizes and not its own.
Fixes: e2af4e403c1 ("crypto/scheduler: support DOCSIS security protocol")
Cc: stable@dpdk.org
Signed-off-by: Julien Hascoet <jhascoet@kalrayinc.com>
---
drivers/crypto/scheduler/scheduler_pmd_ops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/scheduler/scheduler_pmd_ops.c b/drivers/crypto/scheduler/scheduler_pmd_ops.c
index a18f7a08b0..6e43438469 100644
--- a/drivers/crypto/scheduler/scheduler_pmd_ops.c
+++ b/drivers/crypto/scheduler/scheduler_pmd_ops.c
@@ -185,7 +185,7 @@ scheduler_session_size_get(struct scheduler_ctx *sched_ctx,
uint8_t session_type)
{
uint8_t i = 0;
- uint32_t max_priv_sess_size = 0;
+ uint32_t max_priv_sess_size = sizeof(struct scheduler_session_ctx);
/* Check what is the maximum private session size for all workers */
for (i = 0; i < sched_ctx->nb_workers; i++) {
--
2.34.1
next reply other threads:[~2024-07-02 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 7:50 jhascoet [this message]
2024-07-05 7:34 jhascoet
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=20240702075052.1697714-1-jhascoet@kalrayinc.com \
--to=ju.hascoet@gmail.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=david.coyle@intel.com \
--cc=dev@dpdk.org \
--cc=jhascoet@kalrayinc.com \
--cc=kai.ji@intel.com \
--cc=kevin.osullivan@intel.com \
--cc=stable@dpdk.org \
/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).