From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Anoob Joseph <anoobj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "suanmingm@nvidia.com" <suanmingm@nvidia.com>,
"kai.ji@intel.com" <kai.ji@intel.com>,
"brian.dooley@intel.com" <brian.dooley@intel.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: RE: [PATCH] doc: add limitation in using segment-sz in crypto-perf
Date: Mon, 19 May 2025 06:03:04 +0000 [thread overview]
Message-ID: <DB9PR04MB933212489C153DFA34CED89F899CA@DB9PR04MB9332.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <PH0PR18MB46722C2377C833F92C728E30DF93A@PH0PR18MB4672.namprd18.prod.outlook.com>
> -----Original Message-----
> From: Anoob Joseph <anoobj@marvell.com>
> Sent: 16 May 2025 20:11
> To: Akhil Goyal <gakhil@marvell.com>; dev@dpdk.org
> Cc: suanmingm@nvidia.com; kai.ji@intel.com; Hemant Agrawal
> <hemant.agrawal@nxp.com>; brian.dooley@intel.com; Akhil Goyal
> <gakhil@marvell.com>
> Subject: RE: [PATCH] doc: add limitation in using segment-sz in crypto-perf
> Importance: High
>
> > Subject: [PATCH] doc: add limitation in using segment-sz in
> > crypto-perf
> >
> > When segment-sz is given as parameter, use buffer-sz in descending
> > order.
> > The reason is, same scatter gather buffer list is being used for all
> > packet sizes which is initialized once in the beginning.
> > Now if a small packet case is run first, mbuf SG list will be trimmed
> > to a smaller number of SG and rest of the SGs are lost resulting in segfault.
> > Buffers cannot be re-initialized as that will come in datapath and will be
> costly.
> > So to workaround this, if segment-sz is passed as argument, use values
> > in buffer-sz in descending order.
> >
> > Signed-off-by: Akhil Goyal <gakhil@marvell.com>
>
> Acked-by: Anoob Joseph <anoobj@marvell.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
prev parent reply other threads:[~2025-05-19 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 12:10 Akhil Goyal
2025-05-16 14:41 ` Anoob Joseph
2025-05-19 6:03 ` Hemant Agrawal [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=DB9PR04MB933212489C153DFA34CED89F899CA@DB9PR04MB9332.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=anoobj@marvell.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.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).