[RFC 1/3] eal: add enhanced lock annotations
    Stephen Hemminger 
    stephen at networkplumber.org
       
    Mon Dec  2 17:13:38 CET 2024
    
    
  
On Mon,  2 Dec 2024 13:53:14 +0100
David Marchand <david.marchand at redhat.com> wrote:
> diff --git a/doc/api/doxy-api.conf.in b/doc/api/doxy-api.conf.in
> index d23352d300..ac490e7631 100644
> --- a/doc/api/doxy-api.conf.in
> +++ b/doc/api/doxy-api.conf.in
> @@ -103,6 +103,18 @@ PREDEFINED              = __DOXYGEN__ \
>                            __rte_shared_trylock_function(x)= \
>                            __rte_assert_shared_lock(x)= \
>                            __rte_unlock_function(x)= \
> +                          __rte_capability(x)= \
> +                          __rte_requires_capability(x)= \
> +                          __rte_acquire_capability(x)= \
> +                          __rte_try_acquire_capability(x)= \
> +                          __rte_release_capability(x)= \
> +                          __rte_assert_capability(x)= \
> +                          __rte_requires_shared_capability(x)= \
> +                          __rte_acquire_shared_capability(x)= \
> +                          __rte_try_acquire_shared_capability(x)= \
> +                          __rte_release_shared_capability(x)= \
> +                          __rte_assert_shared_capability(x)= \
> +                          __rte_exclude_capability(x)= \
>                            __attribute__(x)=
I would suggest shortened names:
	__rte_acquires(x)
	__rte_releases(x)
	__rte_must_hold(x)
Based on the original source of all these lock annotations which is sparse.
    
    
More information about the dev
mailing list