DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Han, YingyaX" <yingyax.han@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"Tu, Lijuan" <lijuan.tu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] build: fix memcpy behaviour regression
Date: Fri, 16 Oct 2020 02:13:24 +0000
Message-ID: <BN7PR11MB2818081DFB311E8E8DEAE86AFF030@BN7PR11MB2818.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201012145148.290451-1-bruce.richardson@intel.com>

Tested-by: Han, Yingya <yingyax.han@intel.com>

Best Regards,
-----Original Message-----
From: Richardson, Bruce <bruce.richardson@intel.com> 
Sent: Monday, October 12, 2020 10:52 PM
To: dev@dpdk.org
Cc: Han, YingyaX <yingyax.han@intel.com>; Ananyev, Konstantin <konstantin.ananyev@intel.com>; Tu, Lijuan <lijuan.tu@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>
Subject: [PATCH] build: fix memcpy behaviour regression

When testing on some x86 platforms, code compiled with meson was observed running at a different power-license level to that compiled with make. This is due to the fact that meson auto-detects the instruction sets available on the system and enabled AVX512 rte_memcpy when AVX512 was available, while on make, a build time AVX-512 flag needed to be explicitly set to enable that AVX512 rte_memcpy code path.

In the absense of runtime path selection for rte_memcpy - which is complicated by it being a static inline function in a header file - we can fix this behaviour regression by similarly having a build-time option which must be set to enable the AVX-512 memcpy path.

  reply	other threads:[~2020-10-16  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 14:51 Bruce Richardson
2020-10-16  2:13 ` Han, YingyaX [this message]
2020-10-17 10:32   ` Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BN7PR11MB2818081DFB311E8E8DEAE86AFF030@BN7PR11MB2818.namprd11.prod.outlook.com \
    --to=yingyax.han@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=lijuan.tu@intel.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git