From: "Liu, Yong" <yong.liu@intel.com>
To: Peng Yuan <yuan.peng@intel.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH v2] test_plans: add test plan of macsec_for_ixgbe
Date: Mon, 27 Feb 2017 11:24:06 +0800 [thread overview]
Message-ID: <58B39BD6.5070602@intel.com> (raw)
In-Reply-To: <1488214610-4561-1-git-send-email-yuan.peng@intel.com>
Yuan,
Look like SA support multi configurations. But in the test plan only
covered index 0. Is there any gap here?
And please remove blank lines in the end of test plan.
Thank,
Marvin
On 02/28/2017 12:56 AM, Peng Yuan wrote:
> +3. added command::
> +
> + testpmd>set macsec offload (port_id) on encrypt (on|off) replay-protect (on|off)
> + " Enable MACsec offload. "
> + testpmd>set macsec offload (port_id) off
> + " Disable MACsec offload. "
> + testpmd>set macsec sc (tx|rx) (port_id) (mac) (pi)
> + " Configure MACsec secure connection (SC). "
> + testpmd>set macsec sa (tx|rx) (port_id) (idx) (an) (pn) (key)
> + " Configure MACsec secure association (SA). "
> +
next prev parent reply other threads:[~2017-02-27 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 16:56 Peng Yuan
2017-02-27 3:24 ` Liu, Yong [this message]
2017-02-27 22:55 Peng Yuan
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=58B39BD6.5070602@intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=yuan.peng@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).