From: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, Andre Muezerie <andremue@linux.microsoft.com>
Subject: [PATCH 0/2] compile ipsec on Windows
Date: Mon, 6 Jan 2025 08:45:46 -0800 [thread overview]
Message-ID: <1736181948-8907-1-git-send-email-andremue@linux.microsoft.com> (raw)
Removed VLA for compatibility with MSVC (which does not support VLAs).
Used alloca when a constant fixed length that can be used instead is
not known.
Implementation for rte_ipsec_pkt_crypto_group and
rte_ipsec_ses_from_crypto was moved to new file
lib\ipsec\ipsec_group.c because these functions get exported in a
shared library (lib\ipsec\version.map).
Implementation for rte_ipsec_pkt_crypto_prepare and
rte_ipsec_pkt_process was moved to new file lib\ipsec\ipsec.c because
these functions get exported in a shared library
(lib\ipsec\version.map).
Removed logic which was skipping ipsec on Windows.
Andre Muezerie (2):
lib/ipsec: compile ipsec on Windows
app/test: enable ipsec-related tests
app/test/test_ipsec.c | 17 +----
app/test/test_ipsec_perf.c | 13 ----
app/test/test_ipsec_sad.c | 13 ----
app/test/test_security_inline_proto.c | 26 --------
lib/ipsec/esp_inb.c | 57 +++++++++++-----
lib/ipsec/esp_outb.c | 48 ++++++++++----
lib/ipsec/ipsec.c | 19 ++++++
lib/ipsec/ipsec_group.c | 93 +++++++++++++++++++++++++++
lib/ipsec/ipsec_sad.c | 1 +
lib/ipsec/ipsec_telemetry.c | 1 +
lib/ipsec/meson.build | 10 +--
lib/ipsec/misc.h | 10 ++-
lib/ipsec/rte_ipsec.h | 15 ++---
lib/ipsec/rte_ipsec_group.h | 84 ++----------------------
lib/ipsec/sa.c | 4 +-
15 files changed, 210 insertions(+), 201 deletions(-)
create mode 100644 lib/ipsec/ipsec.c
create mode 100644 lib/ipsec/ipsec_group.c
--
2.47.0.vfs.0.3
next reply other threads:[~2025-01-06 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 16:45 Andre Muezerie [this message]
2025-01-06 16:45 ` [PATCH 1/2] lib/ipsec: " Andre Muezerie
2025-01-06 16:45 ` [PATCH 2/2] app/test: enable ipsec-related tests Andre Muezerie
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=1736181948-8907-1-git-send-email-andremue@linux.microsoft.com \
--to=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
/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).