On 4/12/21 5:19 PM, Gaetan Rivet wrote:
> Expose functions reporting user configuration of offloading threads, as
> well as utility functions for multithreading.
> 
> This will only expose the configuration knob to the user, while no
> datapath will implement the multiple thread request.
> 
> This will allow implementations to use this API for offload thread
> management in relevant layers before enabling the actual dataplane
> implementation.
> 
> The offload thread ID is lazily allocated and can as such be in a
> different order than the offload thread start sequence.
> 
> The RCU thread will sometime access hardware-offload objects from
> a provider for reclamation purposes.  In such case, it will get
> a default offload thread ID of 0. Care must be taken that using
> this thread ID is safe concurrently with the offload threads.
> 
> Signed-off-by: Gaetan Rivet <[email protected]>
> Reviewed-by: Eli Britstein <[email protected]>
> ---
>  lib/netdev-offload-provider.h |  1 +
>  lib/netdev-offload.c          | 88 ++++++++++++++++++++++++++++++++++-
>  lib/netdev-offload.h          | 19 ++++++++
>  vswitchd/vswitch.xml          | 16 +++++++
>  4 files changed, 122 insertions(+), 2 deletions(-)
> 

Reviewed-by: Maxime Coquelin <[email protected]>

Thanks,
Maxime

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to