From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jan Viktorin <viktorin@rehivetech.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/2] disable CONFIG_RTE_SCHED_VECTOR for arm
Date: Fri, 27 Nov 2015 15:49:59 +0100 [thread overview]
Message-ID: <2507086.1M5oHiOpA1@xps13> (raw)
In-Reply-To: <20151127154025.59ad8a18@pcviktorin.fit.vutbr.cz>
2015-11-27 15:40, Jan Viktorin:
> Hello,
>
> this what I was talking about at the Userspace Summit in Dublin...
> Somebody adds a feature or change a default setting and it breaks
> builds of other configurations and platforms. The current build system
> in DPDK is really imperfect.
The issue is due to enablement of a new feature for every platforms without
dependency check.
Actually the patch should disable CONFIG_RTE_SCHED_VECTOR for every non-x86
platforms.
Another fix is discussed in another thread to disable the feature inside the
code if the platform cannot support it (currently AVX is required).
next prev parent reply other threads:[~2015-11-27 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 13:34 Jerin Jacob
2015-11-27 13:34 ` [dpdk-dev] [PATCH v3 1/2] config: arm64: create common arm64 configs under common_arm64 file Jerin Jacob
2015-11-27 13:34 ` [dpdk-dev] [PATCH v3 2/2] config: disable CONFIG_RTE_SCHED_VECTOR for arm Jerin Jacob
2015-11-27 14:36 ` Jan Viktorin
2015-11-29 23:48 ` Jianbo Liu
2015-11-30 5:47 ` Jerin Jacob
2015-11-30 17:03 ` Jianbo Liu
2015-11-30 10:22 ` Jerin Jacob
2015-11-30 18:55 ` Jianbo Liu
2015-11-30 13:27 ` Jan Viktorin
2015-11-30 13:59 ` Thomas Monjalon
2015-11-30 14:04 ` Jan Viktorin
2015-11-30 14:13 ` Thomas Monjalon
2015-11-27 14:40 ` [dpdk-dev] [PATCH v3 0/2] " Jan Viktorin
2015-11-27 14:49 ` Thomas Monjalon [this message]
2015-11-30 16:37 ` Stephen Hemminger
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=2507086.1M5oHiOpA1@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=viktorin@rehivetech.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).