From: "Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>
To: Anoob Joseph <anoobj@marvell.com>, Akhil Goyal <gakhil@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] test/event: increase default queue depth for tests
Date: Wed, 19 Jun 2024 06:53:39 +0000 [thread overview]
Message-ID: <PH0PR11MB5832A5A79A2981C55727DB07E8CF2@PH0PR11MB5832.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240619063250.304825-1-anoobj@marvell.com>
Acked-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
> -----Original Message-----
> From: Anoob Joseph <anoobj@marvell.com>
> Sent: Wednesday, June 19, 2024 12:03 PM
> To: Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>; Akhil Goyal
> <gakhil@marvell.com>
> Cc: Jerin Jacob <jerinj@marvell.com>; dev@dpdk.org
> Subject: [PATCH] test/event: increase default queue depth for tests
>
> With crypto adapter, larger queue depths are desirable since same queue could
> be used from multiple cores at the same time. With devices that are capable of
> doing large bursts, larger queues would help in multi core management of same
> queue.
>
> Increase default queue depth in crypto adapter tests to cater to such use cases.
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> ---
> app/test/test_event_crypto_adapter.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/app/test/test_event_crypto_adapter.c
> b/app/test/test_event_crypto_adapter.c
> index 0c56744ba0..9d38a66bfa 100644
> --- a/app/test/test_event_crypto_adapter.c
> +++ b/app/test/test_event_crypto_adapter.c
> @@ -32,7 +32,7 @@ test_event_crypto_adapter(void)
> #define NUM_MBUFS (8191)
> #define MBUF_CACHE_SIZE (256)
> #define MAXIMUM_IV_LENGTH (16)
> -#define DEFAULT_NUM_OPS_INFLIGHT (128)
> +#define DEFAULT_NUM_OPS_INFLIGHT 1024
> #define MAX_NB_SESSIONS 4
> #define TEST_APP_PORT_ID 0
> #define TEST_APP_EV_QUEUE_ID 0
> --
> 2.45.2
next prev parent reply other threads:[~2024-06-19 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 6:32 Anoob Joseph
2024-06-19 6:53 ` Gujjar, Abhinandan S [this message]
2024-06-26 10:08 ` Jerin Jacob
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=PH0PR11MB5832A5A79A2981C55727DB07E8CF2@PH0PR11MB5832.namprd11.prod.outlook.com \
--to=abhinandan.gujjar@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.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).