From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: disable SCHED_VECTOR in the default config
Date: Thu, 3 Dec 2015 08:46:41 +0100 [thread overview]
Message-ID: <CAATJJ0JJNmLcgt7ghtvT1XK4uTOzT=JqNYDYB0PmWy4WOBPrkw@mail.gmail.com> (raw)
In-Reply-To: <9114451.qGSGGhSn1W@xps13>
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/include/smmintrin.h:67:1: error:
inlining failed in call to always_inline ‘_mm_testz_si128’: target
specific option mismatch
_mm_testz_si128 (__m128i __M, __m128i __V)
So I'd ask to still disable CONFIG_RTE_SCHED_VECTOR in the default
config via my patch.
Kind Regards,
Christian
On Wed, Dec 2, 2015 at 11:14 PM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> 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 config.
>> (=> http://dpdk.org/ml/archives/dev/2015-November/029067.html)
>
> Is your issue fixed with the following patch?
> http://dpdk.org/browse/dpdk/commit/?id=1985903e4454
>
prev parent reply other threads:[~2015-12-03 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 15:13 Christian Ehrhardt
2015-12-01 15:20 ` Stephen Hemminger
2015-12-05 23:28 ` Thomas Monjalon
2015-12-02 22:14 ` Thomas Monjalon
2015-12-03 7:46 ` Christian Ehrhardt [this message]
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='CAATJJ0JJNmLcgt7ghtvT1XK4uTOzT=JqNYDYB0PmWy4WOBPrkw@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).