From: Akhil Goyal <gakhil@marvell.com>
To: Anoob Joseph <anoobj@marvell.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] crypto/octeontx2: increase metabuf pool
Date: Tue, 29 Jun 2021 19:59:24 +0000 [thread overview]
Message-ID: <CO6PR18MB4484F9C5E4F64435F021AC21D8029@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1623406873-7108-1-git-send-email-anoobj@marvell.com>
>
> When used with crypto adapter, metabuf pool would be shared across
> cores. Account for the same in pool size.
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> ---
Series
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2021-06-29 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 10:21 Anoob Joseph
2021-06-11 10:21 ` [dpdk-dev] [PATCH 2/2] crypto/octeontx: " Anoob Joseph
2021-06-29 19:59 ` 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=CO6PR18MB4484F9C5E4F64435F021AC21D8029@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=ktejasree@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).