From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "Laatz, Kevin" <kevin.laatz@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add check for rx offload security flag
Date: Mon, 10 Sep 2018 16:16:25 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260CED673@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <20180904123256.61631-1-kevin.laatz@intel.com>
Hi Kevin,
> -----Original Message-----
> From: Laatz, Kevin
> Sent: Tuesday, September 4, 2018 1:33 PM
> To: dev@dpdk.org
> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>; Laatz, Kevin
> <kevin.laatz@intel.com>
> Subject: [PATCH] app/testpmd: add check for rx offload security flag
>
> Add a check for the DEV_RX_OFFLOAD_SECURITY flag to the
> port_offload_cap_display().
>
> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
> ---
> app/test-pmd/config.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c index
> 14ccd68..4c60c7e 100644
> --- a/app/test-pmd/config.c
> +++ b/app/test-pmd/config.c
> @@ -594,6 +594,15 @@ port_offload_cap_display(portid_t port_id)
> printf("off\n");
> }
>
> + if (dev_info.rx_offload_capa & DEV_RX_OFFLOAD_SECURITY) {
> + printf("RX offload security: ");
> + if (ports[port_id].dev_conf.rxmode.offloads &
> + DEV_RX_OFFLOAD_SECURITY)
> + printf("on\n");
> + else
> + printf("off\n");
> + }
> +
> if (dev_info.tx_offload_capa & DEV_TX_OFFLOAD_VLAN_INSERT) {
> printf("VLAN insert: ");
> if (ports[port_id].dev_conf.txmode.offloads &
> --
> 2.9.5
./devtools/check-git-log.sh -1
Wrong headline lowercase:
app/testpmd: add check for rx offload security flag
Regards,
Bernard.
next prev parent reply other threads:[~2018-09-10 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 12:32 Kevin Laatz
2018-09-07 11:13 ` Ferruh Yigit
2018-09-10 16:16 ` Iremonger, Bernard [this message]
2018-09-10 16:28 ` [dpdk-dev] [PATCH v2] app/testpmd: add check for Rx " Kevin Laatz
2018-09-10 16:55 ` Iremonger, Bernard
2018-09-21 0:51 ` Ferruh Yigit
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=8CEF83825BEC744B83065625E567D7C260CED673@IRSMSX107.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@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).