DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>, Kai Ji <kai.ji@intel.com>,
	"john.mcnamara@intel.com" <john.mcnamara@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	Kevin O'Sullivan <kevin.osullivan@intel.com>,
	jhascoet <ju.hascoet@gmail.com>,
	David Coyle <david.coyle@intel.com>,
	Anoob Joseph <anoobj@marvell.com>
Subject: RE: [EXTERNAL] [PATCH] driver: crypto: scheduler: fix session size computation
Date: Fri, 19 Jul 2024 13:06:36 +0000	[thread overview]
Message-ID: <CO6PR18MB4484CF2FF34E0F9096A6D280D8AD2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240705125756.227677-1-jhascoet@kalrayinc.com>

Hi Kai,
Please review.

> From: Julien Hascoet <ju.hascoet@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 <ju.hascoet@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++) {


  reply	other threads:[~2024-07-19 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05 12:57 jhascoet
2024-07-19 13:06 ` Akhil Goyal [this message]
2024-10-04  9:04   ` [EXTERNAL] " Ji, Kai
2024-10-09 13:57     ` 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=CO6PR18MB4484CF2FF34E0F9096A6D280D8AD2@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=david.coyle@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=ju.hascoet@gmail.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).