linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alexei Starovoitov <ast@plumgrid.com>,
	Daniel Borkmann <daniel@iogearbox.net>
Cc: mtk.manpages@gmail.com, 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 11:58:01 +0200	[thread overview]
Message-ID: <55B0BAA9.4020106@gmail.com> (raw)
In-Reply-To: <55B01535.4080809@plumgrid.com>

On 07/23/2015 12:12 AM, Alexei Starovoitov wrote:
> On 7/22/15 1:10 PM, Michael Kerrisk (man-pages) wrote:
>>         BPF  maps  are  a generic data structure for storage of different
>>         data types.  A  user  process  can  create  multiple  maps  (with
>>         key/value-pairs  being  opaque bytes of data) and access them via
>>         file descriptors.  Differnt eBPF programs  can  access  the  same
>>         maps  in  parallel.  It's up to the user process and eBPF program
>>         to decide what they store inside maps.
> 
> typo in 'Different'

Fixed.

>>     eBPF program types
>>         By picking prog_type, the program author selects a set of  helper
>>         functions that can be called from the eBPF program and the corre‐
>>         sponding format of struct bpf_context (which  is  the  data  blob
>>         passed  into  the eBPF program as the first argument).  For exam‐
>>         ple,     programs     loaded     with     a     prog_type      of
>>         BPF_PROG_TYPE_SOCKET_FILTER  may  call  the bpf_map_lookup_elem()
>>         helper, whereas some other program  types  may  not  be  able  to
>>         employ  this helper.  The set of functions available to eBPF pro‐
>>         grams of a given type may increase in the future.
> 
> overall it's all correct, but today bpf_map_lookup_elem() is allowed
> for all program types. May be change that to:
> "BPF_PROG_TYPE_KPROBE may call the bpf_probe_read() helper"
> since only type_kprobe programs can call it.
> type_sockets/type_sched_* cannot.

Changed, as you suggest.

>>                The bpf_context argument is a pointer to a struct sk_buff.
>>                Programs cannot access the fields of sk_buff directly.
> 
> Probably drop last sentence and replace 'sk_buff' with '__sk_buff'
> in the first? Or for the first version we can drop both sentences.

I did the former.

> The rest looks great. Thank you much!

Thanks,

Michael



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2015-07-23  9:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 18:43 Draft 3 of bpf(2) man page for review 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) [this message]
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

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=55B0BAA9.4020106@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=ast@plumgrid.com \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).