[dpdk-dev] [PATCH] mk: disable SCHED_VECTOR in the default config

2015-12-01 07:20, Stephen Hemminger: > On Tue, 1 Dec 2015 16:13:23 +0100 > Christian Ehrhardt wrote: > > > As it causes issues when building with RTE_MACHINE=default due to SSE4.x > > requirements and in other discussions was so far rated "lightly tested and > > doesn't provide really significan

[dpdk-dev] [PATCH] mk: disable SCHED_VECTOR in the default config

Hi Thomas, no it is not fixed by that commit. Even with it applied the remaining include subsequently at rte_vect.h:67 pulls in x86intrin.h which still ends up including smmintrin.h. Long story short is that the mentioned issues like the following still occur: /usr/lib/gcc/x86_64-linux-gnu/5/inclu

[dpdk-dev] [PATCH] mk: disable SCHED_VECTOR in the default config

Hi, 2015-12-01 16:13, Christian Ehrhardt: > As it causes issues when building with RTE_MACHINE=default due to SSE4.x > requirements and in other discussions was so far rated "lightly tested and > doesn't provide really significant performance improvement" let us disable > that in the default confi

[dpdk-dev] [PATCH] mk: disable SCHED_VECTOR in the default config

As it causes issues when building with RTE_MACHINE=default due to SSE4.x requirements and in other discussions was so far rated "lightly tested and doesn't provide really significant performance improvement" let us disable that in the default config. (=> http://dpdk.org/ml/archives/dev/2015-Novembe

[dpdk-dev] [PATCH] mk: disable SCHED_VECTOR in the default config

On Tue, 1 Dec 2015 16:13:23 +0100 Christian Ehrhardt wrote: > As it causes issues when building with RTE_MACHINE=default due to SSE4.x > requirements and in other discussions was so far rated "lightly tested and > doesn't provide really significant performance improvement" let us disable > that