Update after lookup in map.increment for HASH types
Performing the update before lookup incurs an extra spinlock in the
kernel, which hurts performance. Reorder the code and increment to 1.
The memset is there I believe due to some type mismatch warnings, so I'm
leaving as is rather than doing a direct assign to 1. The resulting code
is optimized away anyway.
Fixes: #1314
Signed-off-by: Brenden Blanco <bblanco@gmail.com>
Showing
Please register or sign in to comment