DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiaoyun Li <xiaoyun.li@intel.com>,
	beilei.xing@intel.com, qi.z.zhang@intel.com
Cc: dev@dpdk.org, zhiyong.yang@intel.com,
	Thomas Monjalon <thomas@monjalon.net>,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v6] net/i40e: add interface to use latest vec path
Date: Mon, 17 Sep 2018 15:14:59 +0100	[thread overview]
Message-ID: <5f583daf-cd66-e675-667f-dc7dabbae97b@intel.com> (raw)
In-Reply-To: <20180917095807.14421-1-xiaoyun.li@intel.com>

On 9/17/2018 10:58 AM, Xiaoyun Li wrote:
> For IA, the AVX2 vector path is only recommended to be used on later
> platforms (identified by AVX512 support, like SKL etc.) This is because
> performance benchmark shows downgrade when running AVX2 vector path on
> early platform (BDW/HSW) in some cases. But we still observe perf gain
> with some real work loading.
> 
> So this patch introduced the new devarg use-latest-supported-vec to
> force the driver always selecting the latest supported vec path. Then
> apps are able to take AVX2 path on early platforms. And this logic can
> be re-used if we will have AVX512 vec path in future.
> 
> This patch only affects IA platforms. The selected vec path would be
> like the following:
>   Without devarg/devarg = 0:
>   Machine	vPMD
>   AVX512F	AVX2
>   AVX2	SSE4.2
>   SSE4.2	SSE4.2
>   <SSE4.2	Not Supported
> 
>   With devarg = 1
>   Machine	vPMD
>   AVX512F	AVX2
>   AVX2	AVX2
>   SSE4.2	SSE4.2
>   <SSE4.2	Not Supported
> 
> Other platforms can also apply the same logic if necessary in future.
> 
> Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com>
> ---
> v6:
>  * Polish the doc and commit log.
>  * Use rte_kvargs_process instead of directly kvlist internals.
> v5:
>  * Simpify the rx set function.
> v4:
>  * Polish the codes.
> v3:
>  * Polish the doc and commit log.
> v2:
>  * Correct the calling of the wrong function last time.
>  * Fix seg fault bug.

Thanks for the update looks good to me.

<...>

> @@ -1078,6 +1078,9 @@ struct i40e_adapter {
>  	uint64_t pctypes_tbl[I40E_FLOW_TYPE_MAX] __rte_cache_min_aligned;
>  	uint64_t flow_types_mask;
>  	uint64_t pctypes_mask;
> +
> +	/* For devargs */
> +	bool use_latest_vec;

For this one checkpatch is giving following warning:

CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible
alignment issues - see: https://lkml.org/lkml/2017/11/21/384

The comment in the link seems valid. What do you think using a basic storage
type for the variable, like uint8_t?


And overall is there any objection to follow this new convention?

  reply	other threads:[~2018-09-17 14:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30  2:16 [dpdk-dev] [PATCH] net/i40e: add interface to choose latest vector path Xiaoyun Li
2018-08-31 11:24 ` [dpdk-dev] [PATCH v2] " Xiaoyun Li
2018-09-04 11:39 ` [dpdk-dev] [PATCH v3] " Xiaoyun Li
2018-09-05 12:21   ` Zhang, Qi Z
2018-09-07  9:23     ` Li, Xiaoyun
2018-09-10 10:17 ` [dpdk-dev] [PATCH v4] " Xiaoyun Li
2018-09-12  7:45   ` Zhang, Qi Z
2018-09-12  7:50     ` Zhang, Qi Z
2018-09-12 10:12 ` [dpdk-dev] [PATCH v5] " Xiaoyun Li
2018-09-13  1:38   ` Zhang, Qi Z
2018-09-13 13:27   ` Ferruh Yigit
2018-09-17  7:12     ` Li, Xiaoyun
2018-09-17  9:58 ` [dpdk-dev] [PATCH v6] net/i40e: add interface to use latest vec path Xiaoyun Li
2018-09-17 14:14   ` Ferruh Yigit [this message]
2018-09-17 14:37     ` Thomas Monjalon
2018-09-18  1:28       ` Li, Xiaoyun
2018-09-18  2:22 ` [dpdk-dev] [PATCH v7] " Xiaoyun Li
2018-09-18 13:01   ` Ferruh Yigit
2018-09-18 13:52     ` Zhang, Qi Z

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=5f583daf-cd66-e675-667f-dc7dabbae97b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=thomas@monjalon.net \
    --cc=xiaoyun.li@intel.com \
    --cc=zhiyong.yang@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).