-----Original Message-----
> Date: Sat, 10 Nov 2018 12:55:34 -0600
> From: Honnappa Nagarahalli <honnappa.nagaraha...@arm.com>
> To: bruce.richard...@intel.com, pablo.de.lara.gua...@intel.com
> CC: dev@dpdk.org, jerin.ja...@caviumnetworks.com, hemant.agra...@nxp.com,
> chao...@linux.vnet.ibm.com, yipeng1.w...@intel.com,
> dharmik.thak...@arm.com, gavin...@arm.com, honnappa.nagaraha...@arm.com,
> n...@arm.com
> Subject: [PATCH v2 1/1] hash: separate lf and rw lock lookup code paths
> X-Mailer: git-send-email 2.17.1
>
>
> The lock-free algorithm has caused significant lookup
> performance regression for certain use cases. The
> regression is attributed to the use of non-relaxed
> memory orderings. 2 versions of the lookup functions
> are created. One that uses the RW lock and the one that
> is lock-free. This restores the performance regression
> caused for use cases that used RW lock version of the
> lookup function.
>
> Fixes: e605a1d36 ("hash: add lock-free r/w concurrency")
> Cc: honnappa.nagaraha...@arm.com
>
> Suggested-by: Jerin Jacob <jerin.ja...@caviumnetworks.com>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagaraha...@arm.com>
> Reviewed-by: Ola Liljedahl <ola.liljed...@arm.com>
> Reviewed-by: Gavin Hu <gavin...@arm.com>
> ---
Acked-by: Jerin Jacob <jerin.ja...@caviumnetworks.com>
Tested-by: Jerin Jacob <jerin.ja...@caviumnetworks.com>
- Reported l3fwd hash regression for ARMv8 platform fixed
with this patch by introducing two different code path(obviously!!)
- Verified lock version of lookup() is same as e605a1d36~1 changeset
+ Thomas,
If there is no objection, please consider this patch into -RC3
