From: Ashwin Sekhar T K <asekhar@marvell.com>
To: <dev@dpdk.org>
Cc: <jerinj@marvell.com>, <skori@marvell.com>,
<skoteshwar@marvell.com>, <pbhagavatula@marvell.com>,
<kirankumark@marvell.com>, <psatheesh@marvell.com>,
<asekhar@marvell.com>, <anoobj@marvell.com>, <gakhil@marvell.com>,
<hkalra@marvell.com>, <ndabilpuram@marvell.com>
Subject: [PATCH] crypto/ipsec_mb: enable compilation for non x86 arch
Date: Fri, 10 Jun 2022 21:51:13 +0530 [thread overview]
Message-ID: <20220610162113.1827884-1-asekhar@marvell.com> (raw)
Enable compilation for non x86 architectures by conditionally
compiling x86 specific code.
Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>
---
drivers/crypto/ipsec_mb/ipsec_mb_private.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/crypto/ipsec_mb/ipsec_mb_private.c b/drivers/crypto/ipsec_mb/ipsec_mb_private.c
index aab42c360c..9ea1110aaf 100644
--- a/drivers/crypto/ipsec_mb/ipsec_mb_private.c
+++ b/drivers/crypto/ipsec_mb/ipsec_mb_private.c
@@ -53,6 +53,7 @@ ipsec_mb_create(struct rte_vdev_device *vdev,
const char *name, *args;
int retval;
+#ifdef RTE_ARCH_X86_64
if (vector_mode == IPSEC_MB_NOT_SUPPORTED) {
/* Check CPU for supported vector instruction set */
if (rte_cpu_get_flag_enabled(RTE_CPUFLAG_AVX512F))
@@ -64,6 +65,7 @@ ipsec_mb_create(struct rte_vdev_device *vdev,
else
vector_mode = IPSEC_MB_SSE;
}
+#endif
init_params.private_data_size = sizeof(struct ipsec_mb_dev_private) +
pmd_data->internals_priv_size;
--
2.25.1
next reply other threads:[~2022-06-10 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 16:21 Ashwin Sekhar T K [this message]
2022-06-17 10:23 ` Zhang, Roy Fan
2022-06-17 10:33 ` Ashwin Sekhar Thalakalath Kottilveetil
2022-06-20 13:39 ` Zhang, Roy Fan
2022-06-21 6:38 ` Ashwin Sekhar Thalakalath Kottilveetil
2022-06-23 8:53 ` Zhang, Roy Fan
2022-06-23 13:26 ` Ashwin Sekhar Thalakalath Kottilveetil
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=20220610162113.1827884-1-asekhar@marvell.com \
--to=asekhar@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@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).