From: David Ahern <dsahern@gmail.com>
To: bimmy.pujari@intel.com, bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, mchehab@kernel.org, ast@kernel.org,
daniel@iogearbox.net, kafai@fb.com, maze@google.com,
ashkan.nikravesh@intel.com
Subject: Re: [PATCH bpf-next v5] bpf: Add bpf_ktime_get_real_ns
Date: Thu, 24 Sep 2020 16:15:21 -0600 [thread overview]
Message-ID: <42da4525-d09e-4be9-7d3c-a4662276b721@gmail.com> (raw)
In-Reply-To: <20200924220736.23002-1-bimmy.pujari@intel.com>
On 9/24/20 4:07 PM, bimmy.pujari@intel.com wrote:
> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> index a22812561064..198e69a6508d 100644
> --- a/include/uapi/linux/bpf.h
> +++ b/include/uapi/linux/bpf.h
> @@ -3586,6 +3586,13 @@ union bpf_attr {
> * the data in *dst*. This is a wrapper of **copy_from_user**\ ().
> * Return
> * 0 on success, or a negative error in case of failure.
> + *
> + * u64 bpf_ktime_get_real_ns(void)
> + * Description
> + * Return the real time in nanoseconds.
> + * See: **clock_gettime**\ (**CLOCK_REALTIME**)
This should be a little more explicit -- something like "See the caveats
regarding use of CLOCK_REALTIME in clock_gettime man page."
> + * Return
> + * Current *ktime*.
> */
> #define __BPF_FUNC_MAPPER(FN) \
> FN(unspec), \
> @@ -3737,6 +3744,7 @@ union bpf_attr {
> FN(inode_storage_delete), \
> FN(d_path), \
> FN(copy_from_user), \
> + FN(ktime_get_real_ns), \
> /* */
>
> /* integer value in 'imm' field of BPF_CALL instruction selects which helper
next prev parent reply other threads:[~2020-09-24 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 22:07 [PATCH bpf-next v5] bpf: Add bpf_ktime_get_real_ns bimmy.pujari
2020-09-24 22:15 ` David Ahern [this message]
2020-09-24 22:27 ` Daniel Borkmann
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=42da4525-d09e-4be9-7d3c-a4662276b721@gmail.com \
--to=dsahern@gmail.com \
--cc=ashkan.nikravesh@intel.com \
--cc=ast@kernel.org \
--cc=bimmy.pujari@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=maze@google.com \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.