From: Thomas Monjalon <thomas@monjalon.net>
To: Fan Zhang <roy.fan.zhang@intel.com>
Cc: dev@dpdk.org, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: add FIPs self test description
Date: Mon, 28 Jan 2019 01:27:59 +0100 [thread overview]
Message-ID: <2651981.lpnT6yVvuJ@xps> (raw)
In-Reply-To: <20190124161607.41009-1-roy.fan.zhang@intel.com>
24/01/2019 17:16, Fan Zhang:
> This patch updates the release note for the newly added self
> test feature of FIPS validation sample application.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
> +* **Added self test support to FIPS validation sample application.**
> +
> + The FIPS validation sample application has been added the KATS self test
> + functionality. The self test is meant for validating the PMD during the
> + system initialization. During the test a series of security operations
> + (cipher, hash, aead, etc.) are performed and checked the known answers.
> + Once any result does not match the answer the PMD is uninitialized and
> + removed from the system.
Not sure it is significant enough to appear in the new features of DPDK.
prev parent reply other threads:[~2019-01-28 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 16:16 Fan Zhang
2019-01-28 0:27 ` Thomas Monjalon [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=2651981.lpnT6yVvuJ@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.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).