[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190403203403.4b6d135d@carbon>
Date: Wed, 3 Apr 2019 20:34:03 +0200
From: Jesper Dangaard Brouer <brouer@...hat.com>
To: Stanislav Fomichev <sdf@...gle.com>
Cc: brouer@...hat.com, netdev@...r.kernel.org, bpf@...r.kernel.org,
davem@...emloft.net, ast@...nel.org, daniel@...earbox.net,
simon.horman@...ronome.com, willemb@...gle.com,
peterpenkov96@...il.com
Subject: Re: [PATCH bpf 5/5] flow_dissector: document BPF flow dissector
environment
On Mon, 1 Apr 2019 13:57:34 -0700
Stanislav Fomichev <sdf@...gle.com> wrote:
> diff --git a/Documentation/networking/bpf_flow_dissector.txt b/Documentation/networking/bpf_flow_dissector.txt
> new file mode 100644
> index 000000000000..513be8e20afb
> --- /dev/null
> +++ b/Documentation/networking/bpf_flow_dissector.txt
It looks like you use the RST format, but you use suffix .txt and not .rst.
If you don't know, these files get rendered on:
https://www.kernel.org/doc/html/latest/bpf/index.html
And GitHub also render this stuff e.g.
https://github.com/torvalds/linux/blob/master/Documentation/bpf/bpf_devel_QA.rst
> @@ -0,0 +1,115 @@
> +==================
> +BPF Flow Dissector
> +==================
> +
> +Overview
> +========
> +
> +Flow dissector is a routine that parses metadata out of the packets. It's
> +used in the various places in the networking subsystem (RFS, flow hash, etc).
> +
> +BPF flow dissector is an attempt to reimplement C-based flow dissector logic
> +in BPF to gain all the benefits of BPF verifier (namely, limits on the
> +number of instructions and tail calls).
> +
> +API
> +===
> +
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
Powered by blists - more mailing lists