From: Daniel Borkmann <daniel@iogearbox.net>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Alexei Starovoitov <ast@plumgrid.com>
Cc: linux-man <linux-man@vger.kernel.org>,
linux-kernel@vger.kernel.org, Silvan Jegen <s.jegen@gmail.com>,
Walter Harms <wharms@bfs.de>
Subject: Re: Draft 3 of bpf(2) man page for review
Date: Thu, 23 Jul 2015 15:39:41 +0200 [thread overview]
Message-ID: <55B0EE9D.7000600@iogearbox.net> (raw)
In-Reply-To: <55B0EDD7.8020407@gmail.com>
On 07/23/2015 03:36 PM, Michael Kerrisk (man-pages) wrote:
...
>> Ok, I guess we could revisit/clarify that at a later point in time. I'd add
>> a TODO comment to the source or the like, as this also is related to the 2nd
>> below use case (aggregation/accounting), where an array is typically used.
>
> Okay. FIXME added.
Great.
[...]
>> I'd maybe only mention in addition that in log_level=0 case, we also must not
>> provide a log_buf and log_size, otherwise we get EINVAL.
>
> I changed the text to:
>
> * log_level verbosity level of the verifier. A value of zero
> means that the verifier will not provide a log; in this case,
> log_buf must be a NULL pointer, and log_size must be zero.
Ok.
[...]
> Thanks for clearing that up -- I added the following sentence
>
> JIT compiler for eBPF is currently available for the x86-64, arm64,
> and s390 architectures.
>
> Okay?
Yep.
Thanks,
Daniel
prev parent reply other threads:[~2015-07-23 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 18:43 Michael Kerrisk (man-pages)
2015-07-22 19:22 ` Alexei Starovoitov
2015-07-22 20:10 ` Michael Kerrisk (man-pages)
2015-07-22 22:12 ` Alexei Starovoitov
2015-07-23 9:58 ` Michael Kerrisk (man-pages)
2015-07-23 9:31 ` Daniel Borkmann
2015-07-23 11:23 ` Michael Kerrisk (man-pages)
2015-07-23 12:47 ` Daniel Borkmann
2015-07-23 13:36 ` Michael Kerrisk (man-pages)
2015-07-23 13:39 ` 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=55B0EE9D.7000600@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@plumgrid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=s.jegen@gmail.com \
--cc=wharms@bfs.de \
/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
Powered by JetHome