[dpdk-dev] rte_hash thread safe

Stephen Hemminger stephen at networkplumber.org
Tue Apr 24 07:02:24 CEST 2018


On Tue, 24 Apr 2018 09:18:54 +0530
Jerin Jacob <jerin.jacob at caviumnetworks.com> wrote:

> -----Original Message-----
> > Date: Mon, 23 Apr 2018 17:48:50 -0700
> > From: Jim Murphy <jmurphy at arista.com>
> > To: Stephen Hemminger <stephen at networkplumber.org>
> > Cc: Brijesh Singh <brijesh.s.singh at gmail.com>, dev at dpdk.org
> > Subject: Re: [dpdk-dev] rte_hash thread safe
> > 
> > Anecdotally I've heard that the urcu hash implementation is slower than
> > rte_hash based on pure lookup performance. Has anyone considered adding RCU
> > hooks into rte_hash?  
> 
> 
> For one of our internal project on arm64, we did try rte_hash vs URCU hash.
> Based on our results URCU lookup was much better. By default, URCU
> library does not allocate the memory from huge page, But it has some
> plugin based scheme to override the memory allocation scheme to choose
> hugepage using DPDK backend.
> 

Also URCU hash table can be dynamically resized. With DPDK the application
has to guess at the number of hash heads which makes for bad behavior under
small and large workloads. 



More information about the dev mailing list