DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] config: disable CONFIG_RTE_SCHED_VECTOR for arm
Date: Fri, 27 Nov 2015 16:20:17 +0530	[thread overview]
Message-ID: <20151127105014.GA12878@localhost.localdomain> (raw)
In-Reply-To: <2297109.XH6RklrXdH@xps13>

On Fri, Nov 27, 2015 at 11:23:01AM +0100, Thomas Monjalon wrote:
> Hi Jerin,
> 
> 2015-11-27 15:23, Jerin Jacob:
> > 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/defconfig_arm-armv7a-linuxapp-gcc     | 1 +
> >  config/defconfig_arm64-armv8a-linuxapp-gcc   | 1 +
> >  config/defconfig_arm64-thunderx-linuxapp-gcc | 1 +
> >  config/defconfig_arm64-xgene1-linuxapp-gcc   | 1 +
> 
> You would not need to update 4 files if the 3 last ones were including the
> first one.

armv7 and armv8 config parameters are quite different.I think we
can converge all the common configs of defconfig_arm64-*

> I think having an arm config base would also make clearer the differences
> between the arm platforms.

Yes, For armv8, I can update arm64-armv8a-linuxapp-gcc as a base config
and only absolute delta changes can be added to thunderx/xgene1 config.

I will send out the next revision with arm64-armv8a-linuxapp-gcc as
a base config.

Thanks
Jerin

      reply	other threads:[~2015-11-27 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27  9:53 Jerin Jacob
2015-11-27 10:23 ` Thomas Monjalon
2015-11-27 10:50   ` Jerin Jacob [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=20151127105014.GA12878@localhost.localdomain \
    --to=jerin.jacob@caviumnetworks.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).