-----Original Message----- > Date: Sat, 10 Nov 2018 12:55:34 -0600 > From: Honnappa Nagarahalli <[email protected]> > To: [email protected], [email protected] > CC: [email protected], [email protected], [email protected], > [email protected], [email protected], > [email protected], [email protected], [email protected], > [email protected] > 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: [email protected] > > Suggested-by: Jerin Jacob <[email protected]> > Signed-off-by: Honnappa Nagarahalli <[email protected]> > Reviewed-by: Ola Liljedahl <[email protected]> > Reviewed-by: Gavin Hu <[email protected]> > ---
Acked-by: Jerin Jacob <[email protected]> Tested-by: Jerin Jacob <[email protected]> - 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
