[net-next PATCH 3/4] doc/bpf: describes the different types of eBPF maps available

The purpose is to help choose the right map type based on the individual use-case. To start with, only BPF_MAP_TYPE_ARRAY is described. It is the plan that all types should have descriptions here. Signed-off-by: Jesper Dangaard Brouer --- Documentation/bpf/ebpf_maps.rst |3

[net-next PATCH 4/4] doc/bpf: describe BCC the BPF Compiler Collection

It is worth mentioning BCC (BPF Compiler Collection) in-order to direct developers into that community. Reviewed-by: Alexander Alemayhu Signed-off-by: Jesper Dangaard Brouer --- Documentation/bpf/bcc_tool_chain.rst | 37 ++ Documentation/bpf/index.rst

[net-next PATCH 2/4] doc/bpf: document interacting with eBPF maps

Describe what eBPF maps are, how to create them, and how to interact with them. Thanks to Quentin Monnet for improving this document by fixing many typos and early review. Signed-off-by: Jesper Dangaard Brouer --- Documentation/bpf/ebpf_maps.rst | 255

[net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter

ernel/tree/master/kernel/Documentation Thanks to the following people, who have already reviewed and fixed earlier versions of this documentation on the IOvisor mailing-list: Alexander Alemayhu Alexei Starovoitov Daniel Borkmann Quentin Monnet --- Jesper Dangaard Brouer (4): doc/bpf:

[net-next PATCH 1/4] doc/bpf: start eBPF documentation tree bpf/

areas eBFP is used in and early review. Signed-off-by: Jesper Dangaard Brouer --- Documentation/bpf/index.rst | 66 +++ Documentation/index.rst |1 + 2 files changed, 67 insertions(+) create mode 100644 Documentation/bpf/index.rst diff --git a

Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter

On Tue, 7 Feb 2017 08:37:17 -0700 Jonathan Corbet wrote: > On Tue, 07 Feb 2017 15:30:11 +0100 > Jesper Dangaard Brouer wrote: > > > Question: What kernel tree should this go into??? > > > > If going through Jonathan Corbet, will it appear sooner here??? > >

Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter

On Tue, 7 Feb 2017 09:46:08 -0700 Jonathan Corbet wrote: > On Tue, 7 Feb 2017 17:09:08 +0100 > Jesper Dangaard Brouer wrote: > > > > > Question: What kernel tree should this go into??? > > > > > > > > If going through Jonathan Corbet,

Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter

On Tue, 07 Feb 2017 17:43:38 +0100 Daniel Borkmann wrote: > Hi Jesper, > > On 02/07/2017 03:30 PM, Jesper Dangaard Brouer wrote: > > Question: What kernel tree should this go into??? > > > > If going through Jonathan Corbet, will it appear sooner here??? > >

Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter

On Tue, 7 Feb 2017 14:23:23 -0700 Jonathan Corbet wrote: > On Tue, 7 Feb 2017 21:51:49 +0100 > Jesper Dangaard Brouer wrote: > > > I sounds like Daniel (see other email) have bigger plans for what > > Documentation/BPF/ should contain. E.g. consolidating > &g

Re: [RFC bpf-next v2 8/8] bpf: add documentation for eBPF helpers (58-64)

CPUMAP redirect "is not fully implemented" is confusing. The issue is that CPUMAP only works for "native" XDP. What about saying: "[...] or to CPUs (for redirecting XDP frames to another CPU; but this is only implemented for native XDP as of this writing)" -- Best regar

Re: [PATCH net-next 2/2] tools: bpf: add bpftool

a > proper man page? Do you prefer one over the other? I would prefer adding a README.rst file, in RST-format, as the rest of the kernel documentation is moving in that direction[1] (your github version is in README.md format). A man page will always be out-of-sync, and even out-of-sync on dif

Re: [PATCH net-next 2/2] tools: bpf: add bpftool

On Wed, 27 Sep 2017 03:57:42 -0700 Jakub Kicinski wrote: > On Wed, 27 Sep 2017 12:45:11 +0200, Jesper Dangaard Brouer wrote: > > On Wed, 27 Sep 2017 00:02:08 +0100 > > Jakub Kicinski wrote: > > > > > On Tue, 26 Sep 2017 15:24:06 -0700, Alexei Starovoitov wro

Re: [PATCH net-next v3 3/3] tools: bpftool: add documentation

9 > tools/bpf/bpftool/Documentation/bpftool.txt | 34 +++ RST-format files are usually called .rst and not .txt This is useful when people happen to browse the code via github, then they get formatted nicely e.g.: https://github.com/torvalds/linux/blob/master/samples/bpf/READ

XDP (eXpress Data Path) documentation

cs.org page). You got to love it! :-) -- Best regards, Jesper Dangaard Brouer MSc.CS, Principal Kernel Engineer at Red Hat Author of http://www.iptv-analyzer.org LinkedIn: http://www.linkedin.com/in/brouer [3] https://github.com/netoptimizer/prototype-kernel/commits/master -- To unsubscr

Re: [iovisor-dev] XDP (eXpress Data Path) documentation

On Tue, 20 Sep 2016 19:47:07 -0700 Alexei Starovoitov wrote: > On Tue, Sep 20, 2016 at 11:08:44AM +0200, Jesper Dangaard Brouer via > iovisor-dev wrote: > > Hi all, > > > > As promised, I've started documenting the XDP eXpress Data Path): > &g

Re: XDP (eXpress Data Path) documentation

On Wed, 21 Sep 2016 17:03:24 -0700 Tom Herbert wrote: > On Tue, Sep 20, 2016 at 2:08 AM, Jesper Dangaard Brouer > wrote: > > Hi all, > > > > As promised, I've started documenting the XDP eXpress Data Path): > > > > [1] > > https://prototype

Re: XDP (eXpress Data Path) documentation

On Tue, 20 Sep 2016 11:08:44 +0200 Jesper Dangaard Brouer wrote: > As promised, I've started documenting the XDP eXpress Data Path): > > [1] > https://prototype-kernel.readthedocs.io/en/latest/networking/XDP/index.html > > IMHO the documentation have reached a stage

Re: [PATCH bpf-next v3 8/8] bpf: add documentation for eBPF helpers (58-64)

P_REDIRECT** on success, or **XDP_ABORT** on error. > + * "XDP_ABORT" -> "XDP_ABORTED" I don't know if it's worth mentioning in the doc/man-page; that for XDP using bpf_redirect_map() is a HUGE performance advantage, compared to the bpf_redirect() call ? -- Be

Re: [PATCH bpf-next v3 8/8] bpf: add documentation for eBPF helpers (58-64)

On Wed, 18 Apr 2018 15:09:41 +0100 Quentin Monnet wrote: > 2018-04-18 15:34 UTC+0200 ~ Jesper Dangaard Brouer > > On Tue, 17 Apr 2018 15:34:38 +0100 > > Quentin Monnet wrote: > > > >> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h > &g

Re: [PATCH bpf-next v3 8/8] bpf: add documentation for eBPF helpers (58-64)

On Thu, 19 Apr 2018 13:44:41 +0100 Quentin Monnet wrote: > 2018-04-18 17:43 UTC+0200 ~ Jesper Dangaard Brouer > > On Wed, 18 Apr 2018 15:09:41 +0100 > > Quentin Monnet wrote: > > > >> 2018-04-18 15:34 UTC+0200 ~ Jesper Dangaard Brouer > >&

[bpf-next PATCH 0/5] bpf, doc: convert Documentation/bpf to RST-formatting

This patchset have been uploaded as branch bpf_doc10 on github[2], so reviewers can see how GitHub renders this. [2] https://github.com/netoptimizer/linux/tree/bpf_doc10/Documentation/bpf --- Jesper Dangaard Brouer (5): bpf, doc: add basic README.rst file bpf, doc: rename txt files to

[bpf-next PATCH 1/5] bpf, doc: add basic README.rst file

igned-off-by: Jesper Dangaard Brouer --- Documentation/bpf/README.rst | 36 1 file changed, 36 insertions(+) create mode 100644 Documentation/bpf/README.rst diff --git a/Documentation/bpf/README.rst b/Documentation/bpf/README.rst new file mode 100644

[bpf-next PATCH 2/5] bpf, doc: rename txt files to rst files

This will cause them to get auto rendered, e.g. when viewing them on GitHub. Followup patches will correct the content to be RST compliant. Also adjust README.rst to point to the renamed files. Signed-off-by: Jesper Dangaard Brouer --- Documentation/bpf/README.rst|4 Documentation

[bpf-next PATCH 4/5] bpf, doc: convert bpf_devel_QA.rst to use RST formatting

Same story as bpf_design_QA.rst RST format conversion. Again thanks to Quentin Monnet for fixes and patches that have been squashed. Signed-off-by: Jesper Dangaard Brouer --- Documentation/bpf/bpf_devel_QA.rst | 799 +++- 1 file changed, 420 insertions(+), 379

[bpf-next PATCH 3/5] bpf, doc: convert bpf_design_QA.rst to use RST formatting

integrated with kernel-doc project/movement. Signed-off-by: Jesper Dangaard Brouer --- Documentation/bpf/bpf_design_QA.rst | 223 +++ 1 file changed, 144 insertions(+), 79 deletions(-) diff --git a/Documentation/bpf/bpf_design_QA.rst b/Documentation/bpf/bpf_desi

[bpf-next PATCH 5/5] bpf, doc: howto use/run the BPF selftests

I always forget howto run the BPF selftests. Thus, lets add that info to the QA document. Documentation was based on Cilium's documentation: http://cilium.readthedocs.io/en/latest/bpf/#verifying-the-setup Signed-off-by: Jesper Dangaard Brouer --- Documentation/bpf/bpf_devel_QA.rst |

Re: [bpf-next PATCH 5/5] bpf, doc: howto use/run the BPF selftests

On Mon, 14 May 2018 17:15:54 +0200 Silvan Jegen wrote: > Hi > > Some typo fixes below. > > On Mon, May 14, 2018 at 3:43 PM Jesper Dangaard Brouer > wrote: > > I always forget howto run the BPF selftests. Thus, lets add that info > > to the QA document. >

Re: [PATCH 0/3] bpf: add boot parameters for sysctl knobs

ate=%2a [2] https://github.com/netoptimizer/linux/blob/bpf_doc10/Documentation/bpf/bpf_devel_QA.rst#q-how-do-i-indicate-which-tree-bpf-vs-bpf-next-my-patch-should-be-applied-to -- Best regards, Jesper Dangaard Brouer MSc.CS, Principal Kernel Engineer at Red Hat LinkedIn: http://www.linkedin.c

Re: [PATCH bpf-next v2 0/3] bpf: add boot parameters for sysctl knobs

e a difference between the loaded BPF program that got loaded at boot-time with systemd (no constant blinding) and when someone reloads that systemd service after /etc/sysctl.conf have been evaluated and setting bpf_jit_harden (now slower due to constant blinding). This is inconsistent behavior.