[DTrace-devel] [PATCH 37/61] Fix obsolete comment regarding agg latch seq number

[Kris Van Hees]

On Fri, Jul 08, 2022 at 10:45:21AM -0400, eugene.loh--- via DTrace-devel wrote:
> From: Eugene Loh <eugene.loh at oracle.com>
> 
> Signed-off-by: Eugene Loh <eugene.loh at oracle.com>

Reviewed-by: Kris Van Hees <kris.van.hees at oracle.com>

... queued for dev

> ---
>  libdtrace/dt_impl.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/libdtrace/dt_impl.h b/libdtrace/dt_impl.h
> index 149f8b18..b0af2451 100644
> --- a/libdtrace/dt_impl.h
> +++ b/libdtrace/dt_impl.h
> @@ -208,8 +208,8 @@ typedef struct dt_tstring {
>  /*
>   * To provide a lock-free aggregation write mechanism for the producer,
>   * two copies of each aggregation can be used.  A latch sequence number
> - * on each CPU can be incremented to indicate to the consumer which copy
> - * should be read and whether a copy has changed during reading.
> + * for each aggregation can be incremented to indicate to the consumer
> + * which copy should be read and whether a copy has changed during reading.
>   *
>   * Until BPF maps can be mmapped, however, we cannot take advantage of
>   * this technique.  Using only a single-copy, of course, saves precious
> -- 
> 2.18.4
> 
> 
> _______________________________________________
> DTrace-devel mailing list
> DTrace-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/dtrace-devel