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 [thread overview]
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,
Yingya
-----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.
next prev parent 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:
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=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 \
/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).