public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	"Carlos O'Donell" <carlos@systemhalted.org>
Subject: Re: [PATCH v2] sysdeps: Add 'get_fast_jitter' interace in fast-jitter.h
Date: Wed, 27 Apr 2022 13:46:21 -0700	[thread overview]
Message-ID: <CAMe9rOobGU8wLpDoqs0-P3=vZwWaS2ajzf1ifvbG-d-Avu4o9Q@mail.gmail.com> (raw)
In-Reply-To: <20220427201302.2525203-1-goldstein.w.n@gmail.com>

On Wed, Apr 27, 2022 at 1:13 PM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
>
> 'get_fast_jitter' is meant to be used purely for performance
> purposes. In all cases it's used it should be acceptable to get no
> randomness (see default case). An example use case is in setting
> jitter for retries between threads at a lock. There is a
> performance benefit to having jitter, but only if the jitter can
> be generated very quickly and ultimately there is no serious issue
> if no jitter is generated.
>
> The implementation generally uses 'HP_TIMING_NOW' iff it is
> inlined (avoid any potential syscall paths).
> ---
>  sysdeps/generic/fast-jitter.h | 42 +++++++++++++++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
>  create mode 100644 sysdeps/generic/fast-jitter.h
>
> diff --git a/sysdeps/generic/fast-jitter.h b/sysdeps/generic/fast-jitter.h
> new file mode 100644
> index 0000000000..4dd53e3475
> --- /dev/null
> +++ b/sysdeps/generic/fast-jitter.h
> @@ -0,0 +1,42 @@
> +/* Fallback for fast jitter just return 0.
> +   Copyright (C) 2019-2022 Free Software Foundation, Inc.
> +   This file is part of the GNU C Library.
> +
> +   The GNU C Library is free software; you can redistribute it and/or
> +   modify it under the terms of the GNU Lesser General Public
> +   License as published by the Free Software Foundation; either
> +   version 2.1 of the License, or (at your option) any later version.
> +
> +   The GNU C Library is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
> +   Lesser General Public License for more details.
> +
> +   You should have received a copy of the GNU Lesser General Public
> +   License along with the GNU C Library; if not, see
> +   <https://www.gnu.org/licenses/>.  */
> +
> +#ifndef _FAST_JITTER_H
> +# define _FAST_JITTER_H
> +
> +# include <stdint.h>
> +# include <hp-timing.h>
> +
> +/* Baseline just return 0.  We could create jitter using a clock or
> +   'random_bits' but that may imply a syscall and the goal of
> +   'get_fast_jitter' is minimal overhead "randomness" when such
> +   randomness helps performance.  Adding high overhead the function
> +   defeats the purpose.  */
> +static inline uint32_t
> +get_fast_jitter (void)
> +{
> +# if HP_TIMING_INLINE
> +  hp_timing_t jitter;
> +  HP_TIMING_NOW (jitter);
> +  return (uint32_t) jitter;
> +# else
> +  return 0;
> +# endif
> +}
> +
> +#endif
> --
> 2.25.1
>

LGTM.    An arch can provide a better one if needed.

Reviewed-by: H.J. Lu <hjl.tools@gmail.com>

Thanks.

-- 
H.J.

  reply	other threads:[~2022-04-27 20:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 21:39 [PATCH v1] " Noah Goldstein
2022-04-27 16:25 ` Noah Goldstein
2022-04-27 17:47 ` Adhemerval Zanella
2022-04-27 18:04   ` H.J. Lu
2022-04-27 20:13     ` Noah Goldstein
2022-04-27 20:13 ` [PATCH v2] " Noah Goldstein
2022-04-27 20:46   ` H.J. Lu [this message]
2022-09-11 20:27     ` Sunil Pandey
2022-09-14  1:26       ` Noah Goldstein
2022-09-29  0:11       ` Noah Goldstein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMe9rOobGU8wLpDoqs0-P3=vZwWaS2ajzf1ifvbG-d-Avu4o9Q@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=carlos@systemhalted.org \
    --cc=goldstein.w.n@gmail.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).