From: Nubin Stanley <nubinstanley@gmail.com>
To: users@dpdk.org
Cc: martin.varghese@nokia.com
Subject: [dpdk-users] AES GCM PMD Driver IV length support
Date: Thu, 8 Dec 2016 14:50:31 +0530 [thread overview]
Message-ID: <CAL53N-nP5CHE6FvQ1rZpx18BuYgBnzau+ErQNGBaKoKKLSiOVg@mail.gmail.com> (raw)
Hi All
I see that the only IV size supported in AES GCM driver is 16bytes. For
using AES-GCM-128 in IPsec, the IV length has to be 12 bytes ( 4 (salt)
+ 8 (iv)).
How should I handle this IPsec case with AES GCM PMD driver.
.op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
{.sym = {
.xform_type = RTE_CRYPTO_SYM_XFORM_CIPHER,
{.cipher = {
.algo = RTE_CRYPTO_CIPHER_AES_GCM,
.block_size = 16,
.key_size = {
.min = 16,
.max = 16,
.increment = 0
},
.iv_size = {
.min = 16,
.max = 16,
.increment = 0
}
}, }
}, }
Regards,
Nubin Stanley
next reply other threads:[~2016-12-08 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 9:20 Nubin Stanley [this message]
2016-12-08 10:56 ` Trahe, Fiona
2016-12-09 11:00 Nubin Stanley
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=CAL53N-nP5CHE6FvQ1rZpx18BuYgBnzau+ErQNGBaKoKKLSiOVg@mail.gmail.com \
--to=nubinstanley@gmail.com \
--cc=martin.varghese@nokia.com \
--cc=users@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).