DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jianbo Liu <jianbo.liu@linaro.org>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 2/2] config: disable CONFIG_RTE_SCHED_VECTOR for arm
Date: Sun, 29 Nov 2015 18:48:29 -0500	[thread overview]
Message-ID: <20151129234829.GA2913@qq.com> (raw)
In-Reply-To: <1448631268-10692-3-git-send-email-jerin.jacob@caviumnetworks.com>

On Fri, Nov 27, 2015 at 07:04:28PM +0530, Jerin Jacob wrote:
> Commit 42ec27a0178a causes compiling error on arm, as RTE_SCHED_VECTOR
> does support only SSE intrinsic, so disable it till we have neon support.
> 
> Fixes: 42ec27a0178a ("sched: enable SSE optimizations in config")
> 
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> ---
>  config/common_arm64                      | 1 +
>  config/defconfig_arm-armv7a-linuxapp-gcc | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/config/common_arm64 b/config/common_arm64
> index 5e5e303..d6a9cb9 100644
> --- a/config/common_arm64
> +++ b/config/common_arm64
> @@ -46,3 +46,4 @@ CONFIG_RTE_LIBRTE_I40E_PMD=n
>  CONFIG_RTE_LIBRTE_LPM=n
>  CONFIG_RTE_LIBRTE_TABLE=n
>  CONFIG_RTE_LIBRTE_PIPELINE=n
> +CONFIG_RTE_SCHED_VECTOR=n
> diff --git a/config/defconfig_arm-armv7a-linuxapp-gcc b/config/defconfig_arm-armv7a-linuxapp-gcc
> index 82143af..9924ff9 100644
> --- a/config/defconfig_arm-armv7a-linuxapp-gcc
> +++ b/config/defconfig_arm-armv7a-linuxapp-gcc
> @@ -57,6 +57,7 @@ CONFIG_RTE_LIBRTE_ACL=n
>  CONFIG_RTE_LIBRTE_LPM=n
>  CONFIG_RTE_LIBRTE_TABLE=n
>  CONFIG_RTE_LIBRTE_PIPELINE=n
> +CONFIG_RTE_SCHED_VECTOR=n
>  
>  # cannot use those on ARM
>  CONFIG_RTE_KNI_KMOD=n
> -- 
> 2.1.0
> 

Hi Jerin,
In this way, we still have to modify two files each time a new feature
is added but not verified on ARM architectures.
Since disabling those drivers and libs are common for both armv7 and
armv8, can you put them in one config file, for example: common_arm? 
It is not like common_arm64, which is solely for armv8 platform.
Actually, the arm64 common config is defconfig_arm64-armv8a-linuxapp-gcc
you can include it in the thunderx or xgene1 config files respectively,
and overriding some special config if needed.

On the other hand, If we support the features in the future by
replacing SSE intrinsic with NEON, we just need to remove the lines in one place.

Regards,
Jianbo

  parent reply	other threads:[~2015-11-29 15:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 13:34 [dpdk-dev] [PATCH v3 0/2] " 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 [this message]
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
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=20151129234829.GA2913@qq.com \
    --to=jianbo.liu@linaro.org \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.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).