Re: [dpdk-dev] [PATCH] test/interrupt: account for race with callback

2019-09-13 Thread Thomas Monjalon
09/08/2019 11:18, David Marchand: > On Thu, Aug 8, 2019 at 7:38 PM Aaron Conole wrote: > > > > Because the eal interrupt framework can race when invoking the callback > > and a separate unregister call, the test needs to accommodate the chance > > that the two collide. Do this by checking the ret

Re: [dpdk-dev] [PATCH] test/interrupt: account for race with callback

2019-09-13 Thread Aaron Conole
Aaron Conole writes: > Because the eal interrupt framework can race when invoking the callback > and a separate unregister call, the test needs to accommodate the chance > that the two collide. Do this by checking the return value of unregister > against the race-condition flag (EAGAIN). > > Fix

Re: [dpdk-dev] [PATCH] test/interrupt: account for race with callback

2019-08-09 Thread David Marchand
On Thu, Aug 8, 2019 at 7:38 PM Aaron Conole wrote: > > Because the eal interrupt framework can race when invoking the callback > and a separate unregister call, the test needs to accommodate the chance > that the two collide. Do this by checking the return value of unregister > against the race-c

[dpdk-dev] [PATCH] test/interrupt: account for race with callback

2019-08-08 Thread Aaron Conole
Because the eal interrupt framework can race when invoking the callback and a separate unregister call, the test needs to accommodate the chance that the two collide. Do this by checking the return value of unregister against the race-condition flag (EAGAIN). Fixes: f1a6c22424ce ("app/test: updat