From: Jan Viktorin <viktorin@rehivetech.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/3] arm64: acl: add neon based acl implementation
Date: Tue, 3 Nov 2015 11:35:48 +0100 [thread overview]
Message-ID: <20151103113548.3c7d4224@jvn> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836AB8AA2@irsmsx105.ger.corp.intel.com>
On Tue, 3 Nov 2015 10:23:55 +0000
"Ananyev, Konstantin" <konstantin.ananyev@intel.com> wrote:
> > Hi Konstantin,
> > >
> > > On ARM, is there any specific cpu flag that you can use to determine is NEON
> > > isa is supported or not?
> >
> > Yes, on armv7(RTE_CPUFLAG_NEON). On armv8-a NEON is mandatory.
> >
> > > It would be good to avoid extra conditional compilation here if possible.
> > neon acl is verified/ported only on armv8. While adding the armv7 support the
> > check can be extended for cpuflag based on RTE_CPUFLAG_NEON on armv7
>
> Ok, and is there a flag that allows to distinguish between armv7 and arm8 then at runtime?
> It is probably ok like that, but with all that conditional compilations it gets too messy.
> Another thing - if you can distinguish between armv7 and armv8 at runtime, then you probably
> can set alg = RTE_ACL_CLASSIFY_DEFAULT for armv7 and alg = RTE_ACL_CLASSIFY_NEON for arm8?
> Konstantin
The ARMv7 provides "v7l" in the AT_PLATFORM and the ARMv8 gives
"aarach64". However, I am afraid, as these are two distinct platforms
(with distinct cpuflags), we cannot use the cpuflags easily for this.
Is there an API in DPDK which allows to ask globally: "what platform am
I running on?"?
Jan
>
> >
> > > Another question - did I get it right that NEON isa is supported on all
> > > possible RTE_ARCH_ARM64 cpu models you plan to support?
> >
> > Yes
--
Jan Viktorin E-mail: Viktorin@RehiveTech.com
System Architect Web: www.RehiveTech.com
RehiveTech
Brno, Czech Republic
next prev parent reply other threads:[~2015-11-03 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 14:18 [dpdk-dev] [PATCH 0/3] ARM64: NEON ACL implementation Jerin Jacob
2015-11-02 14:18 ` [dpdk-dev] [PATCH 1/3] arm: ret_vector.h improvements Jerin Jacob
2015-11-02 14:18 ` [dpdk-dev] [PATCH 2/3] arm64: acl: add neon based acl implementation Jerin Jacob
2015-11-02 14:18 ` [dpdk-dev] [PATCH 3/3] arm64: defconfig: enabled CONFIG_RTE_LIBRTE_ACL Jerin Jacob
2015-11-02 15:39 ` [dpdk-dev] [PATCH 2/3] arm64: acl: add neon based acl implementation Jan Viktorin
2015-11-02 16:19 ` Jerin Jacob
2015-11-02 17:31 ` Jan Viktorin
2015-11-02 16:54 ` Ananyev, Konstantin
2015-11-03 4:30 ` Jerin Jacob
2015-11-03 10:23 ` Ananyev, Konstantin
2015-11-03 10:35 ` Jan Viktorin [this message]
2015-11-03 13:20 ` Ananyev, Konstantin
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=20151103113548.3c7d4224@jvn \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).