DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Suanming Mou <suanmingm@nvidia.com>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>,
	"g.singh@nxp.com" <g.singh@nxp.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"ciara.power@intel.com" <ciara.power@intel.com>,
	Anoob Joseph <anoobj@marvell.com>
Cc: "shirik@nvidia.com" <shirik@nvidia.com>,
	"matan@nvidia.com" <matan@nvidia.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] [PATCH] test/crypto: increase mbuf data payload size to 4K
Date: Wed, 21 Jul 2021 06:22:28 +0000	[thread overview]
Message-ID: <CO6PR18MB4484CD8B17DB1438CA2CE0AFD8E39@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210720132811.19425-1-suanmingm@nvidia.com>

> Currently, there is vendor which can support bigger crypto data size.
> Increase the default mbuf data payload size to 4K as needed.
> 
> Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> ---
>  app/test/test_cryptodev.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Adding more people.

> diff --git a/app/test/test_cryptodev.h b/app/test/test_cryptodev.h
> index 31e278261a..1cdd84d01f 100644
> --- a/app/test/test_cryptodev.h
> +++ b/app/test/test_cryptodev.h
> @@ -19,7 +19,7 @@
>  #define DEFAULT_NUM_XFORMS              (2)
>  #define NUM_MBUFS                       (8191)
>  #define MBUF_CACHE_SIZE                 (256)
> -#define MBUF_DATAPAYLOAD_SIZE		(2048 +
> DIGEST_BYTE_LENGTH_SHA512)
> +#define MBUF_DATAPAYLOAD_SIZE		(4096 +
> DIGEST_BYTE_LENGTH_SHA512)
>  #define MBUF_SIZE			(sizeof(struct rte_mbuf) + \
>  		RTE_PKTMBUF_HEADROOM + MBUF_DATAPAYLOAD_SIZE)
> 
> --
> 2.25.1


  reply	other threads:[~2021-07-21  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 13:28 [dpdk-dev] " Suanming Mou
2021-07-21  6:22 ` Akhil Goyal [this message]
2021-07-27 18:26   ` [dpdk-dev] [EXT] " 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=CO6PR18MB4484CD8B17DB1438CA2CE0AFD8E39@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=matan@nvidia.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=shirik@nvidia.com \
    --cc=suanmingm@nvidia.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).