From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jianbo Liu Subject: Re: [PATCH] examples/l3fwd: fix NEON instructions Date: Mon, 30 Oct 2017 14:27:09 +0800 Message-ID: <20171030062623.GA26958@arm.com> References: <20171029074807.30785-1-gprathyusha@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: tomasz.kantecki@intel.com, jianbo.liu@linaro.org, guduriprathyusha@gmail.com, dev@dpdk.org To: Guduri Prathyusha Return-path: Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0078.outbound.protection.outlook.com [104.47.1.78]) by dpdk.org (Postfix) with ESMTP id 59F002BEF for ; Mon, 30 Oct 2017 07:28:23 +0100 (CET) Content-Disposition: inline In-Reply-To: <20171029074807.30785-1-gprathyusha@caviumnetworks.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" The 10/29/2017 13:18, Guduri Prathyusha wrote: > To group consecutive packets with same destination port in bursts of 4 > neon intrinsic data types dp1 and dp2 are calculated such that if > dst_port[]=3D{a,b,c,d,e,f,g,h,i...} dp1 should contain: and > dp2 should contain: in the first iteration. dp1 should > be and dp2 should be in the next iteration. dp2 in > the last iteration should be . > > Whereas the existing code incorrectly calculates dp1 as from > second iteration and thus incorrect calculation of dp2 as > in the last iteration. > > This patch fixes the incorrect ARM NEON instructions on dp1 and dp2. > > Fixes: 569b290cdb36 ("examples/l3fwd: add NEON implementation") > > Signed-off-by: Guduri Prathyusha > --- > examples/l3fwd/l3fwd_neon.h | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/examples/l3fwd/l3fwd_neon.h b/examples/l3fwd/l3fwd_neon.h > index 42d50d3c2..1eace4e03 100644 > --- a/examples/l3fwd/l3fwd_neon.h > +++ b/examples/l3fwd/l3fwd_neon.h > @@ -192,13 +192,13 @@ send_packets_multi(struct lcore_conf *qconf, struct= rte_mbuf **pkts_burst, > * dp1: > * > */ > - dp1 =3D vextq_u16(dp1, dp1, FWDSTEP - 1); > + dp1 =3D vextq_u16(dp2, vdupq_n_u16(0), FWDSTEP - 1)= ; > } > > /* > * dp2: > */ > - dp2 =3D vextq_u16(dp1, dp1, 1); > + dp2 =3D vextq_u16(dp1, vdupq_n_u16(0), 1); Sorry, I don't think you need to change this line. Please ignore my comment about it in the last email. > dp2 =3D vsetq_lane_u16(vgetq_lane_u16(dp2, 2), dp2, 3); > lp =3D port_groupx4(&pnum[j - FWDSTEP], lp, dp1, dp2); > > -- > 2.14.1 > -- IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in = any medium. Thank you.