From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Wysocki, JakubX" <jakubx.wysocki@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [PATCH] crypto/scheduler: fix qp_id in scheduler failover
Date: Mon, 20 Jun 2022 09:12:22 +0000 [thread overview]
Message-ID: <PH7PR11MB5817EF3BBBEEC4C6B8C1D8F2B8B09@PH7PR11MB5817.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220615131349.20315-1-jakubx.wysocki@intel.com>
> -----Original Message-----
> From: Wysocki, JakubX <jakubx.wysocki@intel.com>
> Sent: Wednesday, June 15, 2022 2:14 PM
> To: dev@dpdk.org
> Cc: Ji, Kai <kai.ji@intel.com>; Zhang, Roy Fan <roy.fan.zhang@intel.com>;
> Wysocki, JakubX <jakubx.wysocki@intel.com>
> Subject: [PATCH] crypto/scheduler: fix qp_id in scheduler failover
>
> This commit fixes wrong qp_id value in cryptodev scheduler in failover
> mode.
>
> Fixes: 37f075dad1e9 ("crypto/scheduler: add fail-over scheduling mode")
> Cc: roy.fan.zhang@intel.com
>
> Signed-off-by: Jakub Wysocki <jakubx.wysocki@intel.com>
> ---
> drivers/crypto/scheduler/scheduler_failover.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/crypto/scheduler/scheduler_failover.c
> b/drivers/crypto/scheduler/scheduler_failover.c
> index 5023577ef8..247aeb2f22 100644
> --- a/drivers/crypto/scheduler/scheduler_failover.c
> +++ b/drivers/crypto/scheduler/scheduler_failover.c
> @@ -157,6 +157,9 @@ scheduler_start(struct rte_cryptodev *dev)
> ((struct scheduler_qp_ctx *)
> dev->data->queue_pairs[i])->private_qp_ctx;
>
> + sched_ctx->workers[PRIMARY_WORKER_IDX].qp_id = i;
> + sched_ctx->workers[SECONDARY_WORKER_IDX].qp_id = i;
> +
> rte_memcpy(&qp_ctx->primary_worker,
> &sched_ctx->workers[PRIMARY_WORKER_IDX],
> sizeof(struct scheduler_worker));
> --
> 2.17.1
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-06-20 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 13:13 Jakub Wysocki
2022-06-16 8:54 ` Zhang, Roy Fan
2022-06-20 9:12 ` Zhang, Roy Fan [this message]
2022-06-20 17:51 Jakub Wysocki
2022-06-20 22:12 ` Ji, Kai
2022-06-21 10:34 ` 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=PH7PR11MB5817EF3BBBEEC4C6B8C1D8F2B8B09@PH7PR11MB5817.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jakubx.wysocki@intel.com \
--cc=kai.ji@intel.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).