From: Akhil Goyal <gakhil@marvell.com>
To: <hemant.agrawal@nxp.com>
Cc: <declan.doherty@intel.com>, <dev@dpdk.org>, <g.singh@nxp.com>,
<gakhil@marvell.com>
Subject: [dpdk-dev] [PATCH] l2fwd-crypto: align private data size to cache size
Date: Tue, 6 Apr 2021 00:22:57 +0530 [thread overview]
Message-ID: <20210405185257.721468-1-gakhil@marvell.com> (raw)
In-Reply-To: <20210223061307.22765-1-hemant.agrawal@nxp.com>
L2fwd-crypto is passing 24b private data size while packet
pool creation. This patch aligns that private data size
to cache line size for better performance results.
Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
---
app/proc-info/main.c | 2 +-
examples/l2fwd-crypto/main.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
I believe proc-info change is added by mistake in this patch.
Please fix this.
next prev parent reply other threads:[~2021-04-05 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 6:13 Hemant Agrawal
2021-04-05 18:52 ` Akhil Goyal [this message]
2021-04-09 12:56 ` [dpdk-dev] [PATCH v2] " Hemant Agrawal
2021-04-13 13:00 ` [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=20210405185257.721468-1-gakhil@marvell.com \
--to=gakhil@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.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).