DPDK patches and discussions
 help / color / mirror / Atom feed
From: Volodymyr Fialko <vfialko@marvell.com>
To: <dev@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
	Fan Zhang <roy.fan.zhang@intel.com>
Cc: <jerinj@marvell.com>, Volodymyr Fialko <vfialko@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>
Subject: [PATCH v2 2/2] test/crypto: add L4 checksum case for transport mode
Date: Wed, 23 Feb 2022 11:40:46 +0100	[thread overview]
Message-ID: <20220223104046.1231153-3-vfialko@marvell.com> (raw)
In-Reply-To: <20220223104046.1231153-1-vfialko@marvell.com>

Added test case to verify L4 checksum offload in IPsec transport mode.

Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
Acked-by: Anoob Joseph <anoobj@marvell.com>
---
 app/test/test_cryptodev.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index 694b073f4f..a0c8926776 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -9724,6 +9724,17 @@ test_ipsec_proto_transport_v4(const void *data __rte_unused)
 	return test_ipsec_proto_all(&flags);
 }
 
+static int
+test_ipsec_proto_transport_l4_csum(const void *data __rte_unused)
+{
+	struct ipsec_test_flags flags = {
+		.l4_csum = true,
+		.transport = true,
+	};
+
+	return test_ipsec_proto_all(&flags);
+}
+
 static int
 test_ipsec_proto_stats(const void *data __rte_unused)
 {
@@ -15096,6 +15107,10 @@ static struct unit_test_suite ipsec_proto_testsuite  = {
 			"Transport IPv4",
 			ut_setup_security, ut_teardown,
 			test_ipsec_proto_transport_v4),
+		TEST_CASE_NAMED_ST(
+			"Transport l4 checksum",
+			ut_setup_security, ut_teardown,
+			test_ipsec_proto_transport_l4_csum),
 		TEST_CASE_NAMED_ST(
 			"Statistics: success",
 			ut_setup_security, ut_teardown,
-- 
2.25.1


      parent reply	other threads:[~2022-02-23 10:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 12:52 [PATCH 0/2] Add new IPsec test cases Volodymyr Fialko
2022-02-18 12:52 ` [PATCH 1/2] test/crypto: add TTL and hop limit decrement cases Volodymyr Fialko
2022-02-18 12:52 ` [PATCH 2/2] test/crypto: add L4 checksum case for transport mode Volodymyr Fialko
2022-02-22 19:41 ` [EXT] [PATCH 0/2] Add new IPsec test cases Akhil Goyal
2022-02-23 10:40 ` [PATCH v2 " Volodymyr Fialko
2022-02-23 10:40   ` [PATCH v2 1/2] test/crypto: add TTL and hop limit decrement cases Volodymyr Fialko
2022-02-23 10:48     ` Akhil Goyal
2022-02-23 10:40   ` Volodymyr Fialko [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=20220223104046.1231153-3-vfialko@marvell.com \
    --to=vfialko@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=roy.fan.zhang@intel.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).