All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: David Ahern <dsahern@gmail.com>,
	bimmy.pujari@intel.com, bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, mchehab@kernel.org, ast@kernel.org,
	kafai@fb.com, maze@google.com, ashkan.nikravesh@intel.com
Subject: Re: [PATCH bpf-next v5] bpf: Add bpf_ktime_get_real_ns
Date: Fri, 25 Sep 2020 00:27:03 +0200	[thread overview]
Message-ID: <5a4c7ac0-254b-bd25-8eeb-1bef86cd374f@iogearbox.net> (raw)
In-Reply-To: <42da4525-d09e-4be9-7d3c-a4662276b721@gmail.com>

On 9/25/20 12:15 AM, David Ahern wrote:
> 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."

+1, and also other feedback got ignored along the way [0]; please don't just resend
several new revisions in the meantime when there were things that still need to be
addressed. Thanks!

   [0] https://lore.kernel.org/bpf/d232b77c-da79-da1c-e564-e2a5cb64acb6@iogearbox.net/T/#ma2997c90e80329c457eb92e9592e185f27ce222f

      reply	other threads:[~2020-09-24 22:27 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
2020-09-24 22:27   ` Daniel Borkmann [this message]

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=5a4c7ac0-254b-bd25-8eeb-1bef86cd374f@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ashkan.nikravesh@intel.com \
    --cc=ast@kernel.org \
    --cc=bimmy.pujari@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=dsahern@gmail.com \
    --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.