> -----Original Message-----
> From: Honnappa Nagarahalli <honnappa.nagaraha...@arm.com>
> Sent: Saturday, May 2, 2020 1:03 AM
> To: dev@dpdk.org; phil.y...@arm.com; Van Haaren, Harry
> <harry.van.haa...@intel.com>
> Cc: tho...@monjalon.net; david.march...@redhat.com; Ananyev, Konstantin
> <konstantin.anan...@intel.com>; jer...@marvell.com;
> hemant.agra...@nxp.com; Eads, Gage <gage.e...@intel.com>; Richardson,
> Bruce <bruce.richard...@intel.com>; honnappa.nagaraha...@arm.com;
> n...@arm.com; sta...@dpdk.org
> Subject: [PATCH v3 1/6] service: fix race condition for MT unsafe service
>
> The MT unsafe service might get configured to run on another core
> while the service is running currently. This might result in the
> MT unsafe service running on multiple cores simultaneously. Use
> 'execute_lock' always when the service is MT unsafe.
>
> If the service is known to be mmapped on a single lcore,
mmapped is a typo? Just mapped.
> setting the service capability to MT safe will avoid taking
> the lock and improve the performance.
>
> Fixes: e9139a32f6e8 ("service: add function to run on app lcore")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagaraha...@arm.com>
> Reviewed-by: Phil Yang <phil.y...@arm.com>
Acked-by: Harry van Haaren <harry.van.haa...@intel.com>
<snip diff>
