From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Tejasree Kondoj <ktejasree@marvell.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Radu Nicolau <radu.nicolau@intel.com>
Cc: Vamsi Attunuru <vattunuru@marvell.com>,
Narayana Prasad <pathreya@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v3 8/8] crypto/octeontx2: add cryptodev sec enqueue and dequeue routines
Date: Mon, 20 Jul 2020 13:02:51 +0100 [thread overview]
Message-ID: <28abc4a0-5b62-941a-b22d-2039742c53d3@intel.com> (raw)
In-Reply-To: <20200716083931.29092-9-ktejasree@marvell.com>
On 7/16/2020 9:39 AM, Tejasree Kondoj wrote:
> From: Vamsi Attunuru <vattunuru@marvell.com>
>
> This patch adds lookaside IPsec enqueue and dequeue routines.
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
<...>
> @@ -33,6 +34,13 @@ struct otx2_cpt_vf {
> /**< CPT device capabilities */
> };
>
> +struct cpt_meta_info {
> + uint64_t deq_op_info[4];
> + uint64_t comp_code_sz;
> + union cpt_res_s cpt_res __rte_aligned(16);
> + struct cpt_request_info cpt_req __rte_aligned(8);
> +};
"struct cpt_request_info" already has cache size alignment (__rte_cache_aligned)
[1].
Trying to align it to 8 bytes is reducing the alignment, gcc & clang seems
silently ignoring this case but icc is giving a warning.
Since it is already ignored, and I assume the real intention is not to reduce
the alignment, can you please remove the above "__rte_aligned(8)"?
@Thomas, it is still good to have icc around to catch additional issues ;)
[1]
http://lxr.dpdk.org/dpdk/v20.05/source/drivers/common/cpt/cpt_common.h#L79
next prev parent reply other threads:[~2020-07-20 12:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 8:39 [dpdk-dev] [PATCH v3 0/8] add OCTEON TX2 lookaside IPsec support Tejasree Kondoj
2020-07-16 8:13 ` Anoob Joseph
2020-07-16 16:32 ` Akhil Goyal
2020-07-16 8:39 ` [dpdk-dev] [PATCH v3 1/8] crypto/octeontx2: move capabilities initialization into probe Tejasree Kondoj
2020-07-16 8:39 ` [dpdk-dev] [PATCH v3 2/8] net/octeontx2: move otx2_sec_session struct to otx2_security.h Tejasree Kondoj
2020-07-16 8:39 ` [dpdk-dev] [PATCH v3 3/8] crypto/octeontx2: add lookaside SA context definitions Tejasree Kondoj
2020-07-16 8:39 ` [dpdk-dev] [PATCH v3 4/8] crypto/octeontx2: add cryptodev sec registration Tejasree Kondoj
2020-07-16 8:39 ` [dpdk-dev] [PATCH v3 5/8] crypto/octeontx2: add cryptodev sec capabilities Tejasree Kondoj
2020-07-16 8:39 ` [dpdk-dev] [PATCH v3 6/8] crypto/octeontx2: add cryptodev sec misc callbacks Tejasree Kondoj
2020-07-16 8:39 ` [dpdk-dev] [PATCH v3 7/8] crypto/octeontx2: add cryptodev sec session create Tejasree Kondoj
2020-07-16 8:39 ` [dpdk-dev] [PATCH v3 8/8] crypto/octeontx2: add cryptodev sec enqueue and dequeue routines Tejasree Kondoj
2020-07-20 12:02 ` Ferruh Yigit [this message]
2020-07-20 17:20 ` [dpdk-dev] [EXT] " Tejasree Kondoj
2020-07-20 18:13 ` Ferruh Yigit
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=28abc4a0-5b62-941a-b22d-2039742c53d3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=ktejasree@marvell.com \
--cc=pathreya@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=thomas@monjalon.net \
--cc=vattunuru@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).