Would be great if you could submit some of the missing pieces to linux-man@... for bpf(2) man-page inclusion while at it, so this doesn't need to be done twice. Thanks for

Brendan Gregg <brendan.d.gregg@...> wrote: Hi Brendan, I also included BCC in my documentation, please correct me: http://prototype-kernel.readthedocs.io/en/latest/bpf/bcc_tool_chain.html

Jesper Dangaard Brouer <brouer@...> wrote: I documented this myself, please correct me. http://prototype-kernel.readthedocs.io/en/latest/bpf/ebpf_maps.html#creating-a-map

Alexei Starovoitov <alexei.starovoitov@...> wrote: Thanks, I'm using that to write some doc. http://prototype-kernel.readthedocs.io/en/latest/bpf/ebpf_maps.html Gotten to BPF_MAP_TYPE_ARRAY

I don't expect it to change any time soon, but it can.

Awesome, thanks Derek and Alexei! I'm going to submit a PR that enables the following: TRACEPOINT_PROBE(net, net_dev_start_xmit) { char devname[16]; TP_DATA_LOC_READ_CONST(&devname[0], name,

<iovisor-dev@...> wrote: pretty much what Derek said. Just one more point to add: - this is kernel internal data, so layout can change at any time. yeah that's a bug. bcc needs to have

iovisor-dev <iovisor-dev@...> wrote: yeah. definitely would be great to add map descriptions to the kernel docs. So far most of it is in commit logs. git log kernel/bpf/arraymap.c|tail

Hi Sasha > 1) How do we get access to the __data_loc field? (I can fetch the same info from skb->dev->name but if there's a way to work with the __data_loc field directly, it's even better.) It is a

Thanks! - this seem rather BCC specific syntax, and I'm looking for documentation close for the kernel (samples/bpf/). The best documentation I found was the man-page for the syscall bpf(2):

Hi all, I'm trying to attach a BPF program to a tracepoint that has a __string field, such as net:net_dev_start_xmit. This tracepoint has the following format (from debugfs/events/.../format): name:

I did some in the bcc ref guide, but it's incomplete, and the bcc versions: https://github.com/iovisor/bcc/blob/master/docs/reference_guide.md Brendan

Hi IOvisor/eBPF people, Do we have some documentation on eBPF maps? Like that map types are available, and what they are useful for? Notice, just list listing[1] the enum is not so useful: enum

Please join us for our bi-weekly call. As usual, this meeting is open to everybody and completely optional. You might be interested to join if: You want to know what is going on in BPF land You are

<brouer@...> wrote: err=N is errno code. 22=EINVAL since EINVAL and others are so overloaded, there was no point printing traditional 'Invalid argument' in such case, since it would be even

Depends where you look. F.e. tc has 'tc exec bpf dbg' to find the mount and dump the trace pipe. Yep, see discussion from netdev: https://www.spinics.net/lists/netdev/msg406926.html

Jesper Dangaard Brouer <brouer@...> wrote: (So, let me answer my own question.) The trace "printk" output goes into: /sys/kernel/debug/tracing/trace_pipe And samples/bpf have a function

Hi IOvisor-group, I'm playing with kernels samples/bpf, and want so advice on debugging eBPF programs. First question: I noticed bpf_trace_printk(), but nothing shows up when I'm using it... what

dhcp function is a slow path and has quite a bit of complexity that is not appropriate for datapath. Normal dhcp is handled by user space dhclient. So I think it would be better to do the same in your

Hello, We are having some issues for handling the address pool of a DHCP server implemented with eBPF. We tried to implement it using a map containing all the available addresses, this map is filled