From: Akhil Goyal <gakhil@marvell.com>
To: Ciara Power <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>,
Kevin O'Sullivan <kevin.osullivan@intel.com>
Subject: RE: [EXT] [PATCH 1/2] test/crypto-perf: fix number of sessions for cores
Date: Tue, 15 Nov 2022 09:30:59 +0000 [thread overview]
Message-ID: <CO6PR18MB448467DF8F044F4DA1269B43D8049@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221114165748.307086-1-ciara.power@intel.com>
> Currently the performance application creates a device session per lcore.
> This was not reflected in how many session objects were available
> in the mempool, when using a scheduler device.
>
> The number of lcores is now taken into consideration when calculating
> how many sessions are needed for the scheduler.
>
> Fixes: 09fcf99dcad2 ("test/crypto-perf: fix number of scheduler sessions")
>
> Reported-by: Kevin O'Sullivan <kevin.osullivan@intel.com>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
Series applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2022-11-15 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 16:57 Ciara Power
2022-11-14 16:57 ` [PATCH 2/2] test/crypto-perf: replace slave with worker Ciara Power
2022-11-15 9:30 ` Akhil Goyal [this message]
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=CO6PR18MB448467DF8F044F4DA1269B43D8049@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=kevin.osullivan@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).