From: Stanislaw Kardach <kda@semihalf.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Jerin Jacob <jerinjacobk@gmail.com>,
Kathleen Capella <Kathleen.Capella@arm.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
Dharmik Thakkar <Dharmik.Thakkar@arm.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
Stephen Hemminger <sthemmin@microsoft.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] L3fwd mode in testpmd
Date: Thu, 29 Apr 2021 09:49:45 +0200 [thread overview]
Message-ID: <20210429074945.alquywrvyxjdezqi@toster> (raw)
In-Reply-To: <DBAPR08MB5814F5A1FECAD26722A9F7AC98409@DBAPR08MB5814.eurprd08.prod.outlook.com>
On Wed, Apr 28, 2021 at 09:44:54PM +0000, Honnappa Nagarahalli wrote:
<snip>
> [Honnappa] Sorry, I do not understand this. I see that vector code is under compile time flag as below
>
> #if defined RTE_ARCH_X86 || defined __ARM_NEON
> l3fwd_em_send_packets(nb_rx, pkts_burst,
> portid, qconf);
> #else
> l3fwd_em_no_opt_send_packets(nb_rx, pkts_burst,
> portid, qconf);
> #endif
Take a look at the ifdef tree at the top of l3fwd_em.c, here:
http://git.dpdk.org/dpdk/tree/examples/l3fwd/l3fwd_em.c#n218
#if defined(__SSE2__)
...
#else
#error No vector engine (SSE, NEON, ALTIVEC) available, check your toolchain
#endif
--
Best Regards,
Stanislaw Kardach
next prev parent reply other threads:[~2021-04-29 7:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 18:31 Honnappa Nagarahalli
2021-03-11 6:41 ` Jerin Jacob
2021-03-11 15:18 ` Honnappa Nagarahalli
2021-03-11 15:46 ` Thomas Monjalon
2021-03-11 16:00 ` Honnappa Nagarahalli
2021-03-31 20:35 ` Kathleen Capella
2021-03-31 21:17 ` Jerin Jacob
2021-04-01 0:20 ` Honnappa Nagarahalli
2021-04-01 4:38 ` Jerin Jacob
2021-04-24 0:26 ` Honnappa Nagarahalli
2021-04-26 9:44 ` Jerin Jacob
2021-04-26 17:47 ` Stephen Hemminger
2021-04-26 20:46 ` Honnappa Nagarahalli
2021-04-27 9:39 ` Andrew Rybchenko
2021-04-27 9:50 ` Ferruh Yigit
2021-04-27 9:57 ` Ananyev, Konstantin
2021-04-27 11:11 ` Thomas Monjalon
2021-04-27 11:32 ` Bruce Richardson
2021-04-27 23:26 ` Honnappa Nagarahalli
2021-04-27 23:17 ` Honnappa Nagarahalli
2021-04-28 10:48 ` Bruce Richardson
2021-04-28 11:04 ` Stanisław Kardach
2021-04-28 11:19 ` Thomas Monjalon
2021-04-28 21:44 ` Honnappa Nagarahalli
2021-04-29 7:49 ` Stanislaw Kardach [this message]
2021-04-29 8:31 ` Ananyev, Konstantin
2021-04-29 10:39 ` Stanislaw Kardach
2021-04-29 11:47 ` Ananyev, Konstantin
2021-04-29 11:53 ` Stanislaw Kardach
2021-04-30 11:28 ` Ananyev, Konstantin
2021-08-02 15:07 ` Dharmik Thakkar
2021-04-28 11:17 ` Thomas Monjalon
2021-04-28 10:59 ` Ananyev, Konstantin
2021-04-28 22:10 ` Honnappa Nagarahalli
2021-04-27 16:01 ` Stephen Hemminger
2021-04-27 20:20 ` Honnappa Nagarahalli
2021-04-27 22:23 ` Ananyev, Konstantin
2021-04-27 23:11 ` Honnappa Nagarahalli
2021-04-28 11:00 ` Ananyev, Konstantin
2021-04-26 20:32 ` Honnappa Nagarahalli
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=20210429074945.alquywrvyxjdezqi@toster \
--to=kda@semihalf.com \
--cc=Dharmik.Thakkar@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Kathleen.Capella@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=thomas@monjalon.net \
/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).