From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Cc: dev@dpdk.org, Jan Viktorin <viktorin@rehivetech.com>,
jianbo.liu@linaro.org, jerin.jacob@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH v5] examples/l3fwd: em path performance fix
Date: Fri, 18 Mar 2016 11:04:49 +0100 [thread overview]
Message-ID: <1902439.xcempkFplY@xps13> (raw)
In-Reply-To: <1458294767-5996-1-git-send-email-tomaszx.kulasek@intel.com>
2016-03-18 10:52, Tomasz Kulasek:
> +#if !defined(NO_HASH_MULTI_LOOKUP) && defined(__ARM_NEON)
I think we should use CONFIG_RTE_ARCH_ARM_NEON here.
Any ARM maintainer to confirm?
Note that there is already another occurence of this compiler flag:
examples/l3fwd/l3fwd_em.c:#elif defined(__ARM_NEON)
next prev parent reply other threads:[~2016-03-18 10:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 17:23 [dpdk-dev] [PATCH] " Tomasz Kulasek
2016-03-07 6:19 ` Xu, Qian Q
2016-03-08 12:58 ` [dpdk-dev] [PATCH v2] " Tomasz Kulasek
2016-03-11 11:14 ` Thomas Monjalon
2016-03-11 12:28 ` Kulasek, TomaszX
2016-03-11 12:10 ` [dpdk-dev] [PATCH v3] " Tomasz Kulasek
2016-03-11 16:23 ` Thomas Monjalon
2016-03-11 17:48 ` Kulasek, TomaszX
2016-03-15 14:31 ` Kulasek, TomaszX
2016-03-15 14:49 ` Thomas Monjalon
2016-03-15 16:06 ` Kulasek, TomaszX
2016-03-15 19:42 ` [dpdk-dev] Odp.: " Czekaj, Maciej
2016-03-18 9:36 ` [dpdk-dev] [PATCH v4] " Tomasz Kulasek
2016-03-18 9:43 ` Kulasek, TomaszX
2016-03-18 9:52 ` [dpdk-dev] [PATCH v5] " Tomasz Kulasek
2016-03-18 10:04 ` Thomas Monjalon [this message]
2016-03-18 10:52 ` Jerin Jacob
2016-03-18 11:00 ` Thomas Monjalon
2016-03-18 11:16 ` [dpdk-dev] [PATCH] examples/l3fwd: prefer probed NEON flag to ARM gcc flag Thomas Monjalon
2016-03-18 11:20 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2016-03-18 11:56 ` [dpdk-dev] [PATCH v5] examples/l3fwd: em path performance fix Jan Viktorin
2016-03-18 12:45 ` Kulasek, TomaszX
2016-03-18 12:50 ` Jan Viktorin
2016-03-18 13:31 ` [dpdk-dev] [PATCH v6] " Tomasz Kulasek
2016-03-21 11:57 ` Thomas Monjalon
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=1902439.xcempkFplY@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@linaro.org \
--cc=tomaszx.kulasek@intel.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).