Re: [dpdk-dev] [PATCH] test/mcslock: wait for lcore completion

2019-08-08 Thread Thomas Monjalon
08/08/2019 05:44, Phil Yang (Arm Technology China): > From: Aaron Conole > > > > It's possible that the mcsunlock occurs before the test_mcslock_try has > > a chance to execute, which will result in the trylock being successful, > > making the test case fail. Fix this by waiting until all lcores

Re: [dpdk-dev] [PATCH] test/mcslock: wait for lcore completion

2019-08-07 Thread David Marchand
On Wed, Aug 7, 2019 at 4:58 PM Aaron Conole wrote: > > It's possible that the mcsunlock occurs before the test_mcslock_try has > a chance to execute, which will result in the trylock being successful, > making the test case fail. Fix this by waiting until all lcores have > completed their test be

Re: [dpdk-dev] [PATCH] test/mcslock: wait for lcore completion

2019-08-07 Thread Phil Yang (Arm Technology China)
> -Original Message- > From: Aaron Conole > Sent: Wednesday, August 7, 2019 10:59 PM > To: dev@dpdk.org > Cc: Phil Yang (Arm Technology China) ; Gavin Hu (Arm > Technology China) ; Honnappa Nagarahalli > > Subject: [PATCH] test/mcslock: wait for lcore completion > > It's possible that th

[dpdk-dev] [PATCH] test/mcslock: wait for lcore completion

2019-08-07 Thread Aaron Conole
It's possible that the mcsunlock occurs before the test_mcslock_try has a chance to execute, which will result in the trylock being successful, making the test case fail. Fix this by waiting until all lcores have completed their test before unlocking the master lock. Fixes: 32dcb9fd2a22 ("test/mc