Initialize __x86_shared_non_temporal_threshold only if zero
Commit Message
Support setting processor-specific __x86_shared_non_temporal_threshold
value in init_cpu_features.
Tested on x86 and x86-64. Any comments and feebacks?
H.J.
---
* sysdeps/x86/cacheinfo.c (__x86_shared_non_temporal_threshold):
Initialize only if it is zero.
---
sysdeps/x86/cacheinfo.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Comments
There should be a comment before the if saying how and why it might already
be nonzero. The existing comment explaining the rationale for the default
value here should be moved under the if along with the assignment.
On Fri, May 20, 2016 at 2:24 PM, Roland McGrath <roland@hack.frob.com> wrote:
> There should be a comment before the if saying how and why it might already
> be nonzero. The existing comment explaining the rationale for the default
> value here should be moved under the if along with the assignment.
This patch has been superseded by
https://sourceware.org/ml/libc-alpha/2016-05/msg00221.html
@@ -669,5 +669,6 @@ init_cacheinfo (void)
/* The large memcpy micro benchmark in glibc shows that 6 times of
shared cache size is the approximate value above which non-temporal
store becomes faster. */
- __x86_shared_non_temporal_threshold = __x86_shared_cache_size * 6;
+ if (__x86_shared_non_temporal_threshold == 0)
+ __x86_shared_non_temporal_threshold = __x86_shared_cache_size * 6;
}