Re: [dpdk-dev] [PATCH v3 1/3] eal/x86: run-time dispatch over memcpy

2017-10-02 Thread Konstantin Ananyev
Hi Xiaoyun, Just to be a bit more specific about what I suggest - here is a draft patch below. It still needs more testing and probably polishing, but I suppose gives you an idea. Konstantin --- lib/librte_eal/bsdapp/eal/Makefile | 20 + lib/librte_eal/common/arch/x86/rte_memcpy

Re: [dpdk-dev] [PATCH v3 1/3] eal/x86: run-time dispatch over memcpy

2017-10-01 Thread Li, Xiaoyun
Hi > That means that each file with '#include will have its own > copy > of that function: > $ objdump -d x86_64-native-linuxapp-gcc/app/testpmd | grep > ':' | sort -u | wc -l > 233 > Same story for rte_memcpy_ptr and rte_memcpy_DEFAULT, etc... > Obviously we need (and want) only one copy of th

Re: [dpdk-dev] [PATCH v3 1/3] eal/x86: run-time dispatch over memcpy

2017-10-01 Thread Ananyev, Konstantin
Hi Xiaoyun, > This patch dynamically selects functions of memcpy at run-time based > on CPU flags that current machine supports. This patch uses function > pointers which are bind to the relative functions at constrctor time. > In addition, AVX512 instructions set would be compiled only if users >

[dpdk-dev] [PATCH v3 1/3] eal/x86: run-time dispatch over memcpy

2017-09-26 Thread Xiaoyun Li
This patch dynamically selects functions of memcpy at run-time based on CPU flags that current machine supports. This patch uses function pointers which are bind to the relative functions at constrctor time. In addition, AVX512 instructions set would be compiled only if users config it enabled and