All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Guduri Prathyusha <gprathyusha@caviumnetworks.com>
Cc: tomasz.kantecki@intel.com, Jianbo.Liu@arm.com,
	guduriprathyusha@gmail.com, konstantin.ananyev@intel.com,
	dev@dpdk.org
Subject: Re: [PATCH v2] examples/l3fwd: fix aliasing in port grouping
Date: Mon, 6 Nov 2017 09:59:46 +0530	[thread overview]
Message-ID: <20171106042945.GA4073@jerin> (raw)
In-Reply-To: <20171103104351.30181-1-gprathyusha@caviumnetworks.com>

-----Original Message-----
> Date: Fri,  3 Nov 2017 16:13:51 +0530
> From: Guduri Prathyusha <gprathyusha@caviumnetworks.com>
> To: tomasz.kantecki@intel.com
> CC: Jianbo.Liu@arm.com, guduriprathyusha@gmail.com,
>  konstantin.ananyev@intel.com, dev@dpdk.org, Guduri Prathyusha
>  <gprathyusha@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH v2] examples/l3fwd: fix aliasing in port grouping
> X-Mailer: git-send-email 2.14.1
> 
> With -f-strict-aliasing enabled by default from -O2, gcc > 5.x gives
> undefined behavior in port_groupx4 in ARM. 'pn' and 'pnum' are
> two different pointers pointing to same chunk of memory and
> with -f-strict-aliasing the pointers are assumed to be pointing to
> different memory and compiler reorders instructions that depend on
> pnum and pn. This breaks port grouping algorithm.
> 
> This patch eliminates the above problem by introducing a compiler
> barrier between the instructions that depend on pnum, pn and lp.
> 
> Fixes: 569b290cdb36 ("examples/l3fwd: add NEON implementation")
> 
> Signed-off-by: Guduri Prathyusha <gprathyusha@caviumnetworks.com>

Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>

> ---
>  examples/l3fwd/l3fwd_neon.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/examples/l3fwd/l3fwd_neon.h b/examples/l3fwd/l3fwd_neon.h
> index 4bc161394..b319b5a92 100644
> --- a/examples/l3fwd/l3fwd_neon.h
> +++ b/examples/l3fwd/l3fwd_neon.h
> @@ -114,6 +114,7 @@ port_groupx4(uint16_t pn[FWDSTEP + 1], uint16_t *lp, uint16x8_t dp1,
>  
>  	/* update last port counter. */
>  	lp[0] += gptbl[v].lpv;
> +	rte_compiler_barrier();
>  
>  	/* if dest port value has changed. */
>  	if (v != GRPMSK) {
> -- 
> 2.14.1
> 

  reply	other threads:[~2017-11-06  4:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 10:43 [PATCH v2] examples/l3fwd: fix aliasing in port grouping Guduri Prathyusha
2017-11-06  4:29 ` Jerin Jacob [this message]
2017-11-06  8:18   ` Jianbo Liu
2017-11-07  8:12     ` Ferruh Yigit

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=20171106042945.GA4073@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=Jianbo.Liu@arm.com \
    --cc=dev@dpdk.org \
    --cc=gprathyusha@caviumnetworks.com \
    --cc=guduriprathyusha@gmail.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=tomasz.kantecki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.