DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ji, Kai" <kai.ji@intel.com>
To: jhascoet <ju.hascoet@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: jhascoet <jhascoet@gmail.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"O'Sullivan, Kevin" <kevin.osullivan@intel.com>,
	"Coyle, David" <david.coyle@intel.com>,
	Ciara Power <ciara.power@intel.com>,
	Anoob Joseph <anoobj@marvell.com>
Subject: Re: [PATCH] driver: crypto: scheduler: fix session size computation
Date: Mon, 30 Sep 2024 11:33:00 +0000	[thread overview]
Message-ID: <DS0PR11MB7458A0FDB42386627AA4AA7A81762@DS0PR11MB7458.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240705083503.218315-1-jhascoet@kalrayinc.com>

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

Acked-by: Kai Ji <kai.ji@intel.com>

________________________________
From: jhascoet <ju.hascoet@gmail.com>
Sent: 05 July 2024 09:35
To: dev@dpdk.org <dev@dpdk.org>
Cc: jhascoet <jhascoet@gmail.com>; stable@dpdk.org <stable@dpdk.org>; Ji, Kai <kai.ji@intel.com>; O'Sullivan, Kevin <kevin.osullivan@intel.com>; Coyle, David <david.coyle@intel.com>; Ciara Power <ciara.power@intel.com>; Anoob Joseph <anoobj@marvell.com>
Subject: [PATCH] driver: crypto: scheduler: fix session size computation

From: jhascoet <jhascoet@gmail.com>

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@gmail.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


[-- Attachment #2: Type: text/html, Size: 2918 bytes --]

  reply	other threads:[~2024-09-30 11:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05  8:35 jhascoet
2024-09-30 11:33 ` Ji, Kai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-05 12:57 jhascoet
2024-07-05  7:34 jhascoet
2024-07-02  7:50 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=DS0PR11MB7458A0FDB42386627AA4AA7A81762@DS0PR11MB7458.namprd11.prod.outlook.com \
    --to=kai.ji@intel.com \
    --cc=anoobj@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=david.coyle@intel.com \
    --cc=dev@dpdk.org \
    --cc=jhascoet@gmail.com \
    --cc=ju.hascoet@gmail.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).