11/11/2018 08:48, Jerin Jacob:
> >
> > 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>
Applied, thanks
