[dpdk-dev] [PATCH v2 1/2] test/hash: use existing lcore API

Maxime Coquelin maxime.coquelin at redhat.com
Thu May 23 14:48:17 CEST 2019



On 5/22/19 5:06 PM, David Marchand wrote:
> Prefer the existing apis rather than direct access the configuration
> structure.
> 
> test_hash_multi_add_lookup() currently starts n readers and N writers
> using rte_eal_remote_launch().
> It then waits for the N writers to complete with a custom
> multi_writer_done[] array to synchronise over.
> Jump on the occasion to use rte_eal_wait_lcore() so that the code is
> more straightforward:
> - we start n readers with rte_eal_remote_launch(),
> - we start N writers with rte_eal_remote_launch(),
> - we wait for N writers to join with rte_eal_wait_lcore(),
> - we wait for n readers to join with rte_eal_wait_lcore(),
> 
> Fixes: c7eb0972e74b ("test/hash: add lock-free r/w concurrency")
> Fixes: 3f9aab961ed3 ("test/hash: check lock-free extendable bucket")
> Cc: stable at dpdk.org
> 
> Signed-off-by: David Marchand <david.marchand at redhat.com>
> ---
>   app/test/test_hash_readwrite_lf.c | 41 ++++++++++++++++++---------------------
>   1 file changed, 19 insertions(+), 22 deletions(-)
> 


Reviewed-by: Maxime Coquelin <maxime.coquelin at redhat.com>


More information about the dev mailing list