For example with jit_harden, there will be 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).
[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.com/in/bro
On Mon, 14 May 2018 17:15:54 +0200
Silvan Jegen <s.je...@gmail.com> wrote:
> Hi
>
> Some typo fixes below.
>
> On Mon, May 14, 2018 at 3:43 PM Jesper Dangaard Brouer <bro...@redhat.com>
> wrote:
> > I always forget howto run the BPF selftests. Thus, lets
d-goal is for this to become
more integrated with kernel-doc project/movement.
Signed-off-by: Jesper Dangaard Brouer <bro...@redhat.com>
---
Documentation/bpf/bpf_design_QA.rst | 223 +++
1 file changed, 144 insertions(+), 79 deletions(-)
diff --git a/Docum
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 <bro...@redhat.com>
---
Documentati
Same story as bpf_design_QA.rst RST format conversion.
Again thanks to Quentin Monnet <quentin.mon...@netronome.com> for
fixes and patches that have been squashed.
Signed-off-by: Jesper Dangaard Brouer <bro...@redhat.com>
---
Documentation/bpf/bpf_devel_Q
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 <bro...@redhat.com>
---
Documentation/bpf/READ
-off-by: Jesper Dangaard Brouer <bro...@redhat.com>
---
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 fil
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
On Thu, 19 Apr 2018 13:44:41 +0100
Quentin Monnet <quentin.mon...@netronome.com> wrote:
> 2018-04-18 17:43 UTC+0200 ~ Jesper Dangaard Brouer <bro...@redhat.com>
> > On Wed, 18 Apr 2018 15:09:41 +0100
> > Quentin Monnet <quentin.mon...@netronome.com> wrote:
>
On Wed, 18 Apr 2018 15:09:41 +0100
Quentin Monnet <quentin.mon...@netronome.com> wrote:
> 2018-04-18 15:34 UTC+0200 ~ Jesper Dangaard Brouer <bro...@redhat.com>
> > On Tue, 17 Apr 2018 15:34:38 +0100
> > Quentin Monnet <quentin.mon...@netronome.com> wrote:
>
> + * Return
> + * **XDP_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_r
as of this writing).
Stating that 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 X
On Wed, 27 Sep 2017 03:57:42 -0700
Jakub Kicinski <jakub.kicin...@netronome.com> 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 <jakub.kicin...@netronome.com> wrote:
> >
&
On Tue, 7 Feb 2017 14:23:23 -0700
Jonathan Corbet <cor...@lwn.net> wrote:
> On Tue, 7 Feb 2017 21:51:49 +0100
> Jesper Dangaard Brouer <bro...@redhat.com> wrote:
>
> > I sounds like Daniel (see other email) have bigger plans for what
> > Documentation/BPF/ sh
On Tue, 07 Feb 2017 17:43:38 +0100
Daniel Borkmann <dan...@iogearbox.net> 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
On Tue, 7 Feb 2017 09:46:08 -0700
Jonathan Corbet <cor...@lwn.net> wrote:
> On Tue, 7 Feb 2017 17:09:08 +0100
> Jesper Dangaard Brouer <bro...@redhat.com> wrote:
>
> > > > Question: What kernel tree should this go into???
> > > >
> > > >
On Tue, 7 Feb 2017 08:37:17 -0700
Jonathan Corbet <cor...@lwn.net> wrote:
> On Tue, 07 Feb 2017 15:30:11 +0100
> Jesper Dangaard Brouer <bro...@redhat.com> wrote:
>
> > Question: What kernel tree should this go into???
> >
> > If going through Jona
x.net>
Quentin Monnet <quentin.mon...@6wind.com>
---
Jesper Dangaard Brouer (4):
doc/bpf: start eBPF documentation tree bpf/
doc/bpf: document interacting with eBPF maps
doc/bpf: describes the different types of eBPF maps available
doc/bpf: describe BCC the
com> for improving
this document with areas eBFP is used in and early review.
Signed-off-by: Jesper Dangaard Brouer <bro...@redhat.com>
---
Documentation/bpf/index.rst | 66 +++
Documentation/index.rst |1 +
2 files changed, 67 insertions(+)
Describe what eBPF maps are, how to create them, and how to
interact with them.
Thanks to Quentin Monnet <quentin.mon...@6wind.com> for improving
this document by fixing many typos and early review.
Signed-off-by: Jesper Dangaard Brouer <bro...@redhat.com>
---
Documentation/bpf/e
It is worth mentioning BCC (BPF Compiler Collection) in-order
to direct developers into that community.
Reviewed-by: Alexander Alemayhu <alexan...@alemayhu.com>
Signed-off-by: Jesper Dangaard Brouer <bro...@redhat.com>
---
Documentation/bpf/bcc_tool_chai
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 <bro...@redhat.com>
---
Documentation/bpf/ebpf_ma
On Tue, 20 Sep 2016 11:08:44 +0200 Jesper Dangaard Brouer <bro...@redhat.com>
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 documentat
On Wed, 21 Sep 2016 17:03:24 -0700
Tom Herbert <t...@herbertland.com> wrote:
> On Tue, Sep 20, 2016 at 2:08 AM, Jesper Dangaard Brouer
> <bro...@redhat.com> wrote:
> > Hi all,
> >
> > As promised, I've started documenting the XDP eXpress Data Path):
On Tue, 20 Sep 2016 19:47:07 -0700
Alexei Starovoitov <alexei.starovoi...@gmail.com> 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 P
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 unsubscribe from t
27 matches
Mail list logo
