This is the mail archive of the
mailing list for the glibc project.
RE: [PATCH] x86_64: memcpy/memmove family optimized with AVX512
- From: "Senkevich, Andrew" <andrew dot senkevich at intel dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- Cc: "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>, Carlos O'Donell <codonell at redhat dot com>
- Date: Wed, 13 Jan 2016 18:10:05 +0000
- Subject: RE: [PATCH] x86_64: memcpy/memmove family optimized with AVX512
- Authentication-results: sourceware.org; auth=none
- References: <569547D3 dot 1070002 at linaro dot org>
> On 12-01-2016 12:13, Andrew Senkevich wrote:
>> here is AVX512 implementations of memcpy, mempcpy, memmove,
>> memcpy_chk, mempcpy_chk, memmove_chk.
>> It shows average improvement more than 30% over AVX versions on KNL
>> hardware, performance results attached.
>> Ok for trunk?
> It is too late for 2.23, but ok after review for 2.24.
We would like this patch to be considered for glibc 2.23 since the functionality completes AVX-512 improvements of mem* routines.
Memset tuned for AVX-512 is already checked in so it looks reasonable to have full support in 2.23.
Also the changes are strongly AVX-512 specific, not adding any new interfaces so potential risk of the patch is pretty low.
We already got review comments without any major questions to the patch and fixed version will be ready today.
Given all this can the patch go to current glibc trunk after review is finished?