crypto: add support for testing quad loops in crypto algos

[vpp.git] / src / plugins / unittest / crypto / aes_gcm.c

diff --git a/src/plugins/unittest/crypto/aes_gcm.c b/src/plugins/unittest/crypto/aes_gcm.c
index 764ca9e..3d1b221 100644 (file)
--- a/src/plugins/unittest/crypto/aes_gcm.c
+++ b/src/plugins/unittest/crypto/aes_gcm.c
@@ -264,6 +264,60 @@ UNITTEST_REGISTER_CRYPTO_TEST (aes_gcm256_tc4_chain) = {
     TEST_DATA_CHUNK (tc4_ciphertext256, 40, 20),
   },
 };
+
+UNITTEST_REGISTER_CRYPTO_TEST (aes_gcm256_inc_1024) = {
+  .name = "256-GCM (incr 1024 B)",
+  .alg = VNET_CRYPTO_ALG_AES_256_GCM,
+  .plaintext_incremental = 1024,
+  .key.length = 32,
+  .aad.length = 20,
+  .tag.length = 16,
+};
+
+UNITTEST_REGISTER_CRYPTO_TEST (aes_gcm256_inc1) = {
+  .name = "256-GCM (incr 1056 B)",
+  .alg = VNET_CRYPTO_ALG_AES_256_GCM,
+  .plaintext_incremental = 1024 + 32,
+  .key.length = 32,
+  .aad.length = 20,
+  .tag.length = 16,
+};
+
+UNITTEST_REGISTER_CRYPTO_TEST (aes_gcm256_inc2) = {
+  .name = "256-GCM (incr 1042 B)",
+  .alg = VNET_CRYPTO_ALG_AES_256_GCM,
+  .plaintext_incremental = 1024 + 8,
+  .key.length = 32,
+  .aad.length = 20,
+  .tag.length = 16,
+};
+
+UNITTEST_REGISTER_CRYPTO_TEST (aes_gcm256_inc3) = {
+  .name = "256-GCM (incr 1025 B)",
+  .alg = VNET_CRYPTO_ALG_AES_256_GCM,
+  .plaintext_incremental = 1024 + 1,
+  .key.length = 32,
+  .aad.length = 20,
+  .tag.length = 16,
+};
+
+UNITTEST_REGISTER_CRYPTO_TEST (aes_gcm256_inc4) = {
+  .name = "256-GCM (incr 1009 B)",
+  .alg = VNET_CRYPTO_ALG_AES_256_GCM,
+  .plaintext_incremental = 1024 - 15,
+  .key.length = 32,
+  .aad.length = 20,
+  .tag.length = 16,
+};
+
+UNITTEST_REGISTER_CRYPTO_TEST (aes_gcm256_inc5) = {
+  .name = "256-GCM (incr 1008)",
+  .alg = VNET_CRYPTO_ALG_AES_256_GCM,
+  .plaintext_incremental = 1024 - 16,
+  .key.length = 32,
+  .aad.length = 20,
+  .tag.length = 16,
+};
 /* *INDENT-ON* */
 
 /*