You can also use objcopy: objcopy -I elf64-little -O binary -j.text foo.elf foo.bin The output file will contain just the eBPF instructions.

Hi, Please feel free to join us today at 11am PST (1900 UTC) for another round of IOVisor developer updates and

<mathieu.desnoyers@...> wrote: yep :) please cc iovisor-dev as well for ideas you guys have around making use of bpf kernel bits with 'latency-tracker'.

Hi All, I'm doing my version of hello world for eBPF by forwarding eth frames between two nics - eth1 and eth3 on my machine. Using bpf_clone_redirect(). (cc/export/helpers.h says bpf_redirect is

You need to use BPF.SCHED_ACT or SCHED_CLS to use these forwarding functions. They are disallowed by the verifier for SOCKET_FILTER programs. The simplest usage (focus on the pyroute2 bits) is

Hi, Please feel free to join us tomorrow at 11am PST (1900 UTC) for another round of IOVisor developer updates and discussions. Special on the agenda this week is a half hour or so discussion led by

Sorry interested but it keeps scheduled on top of other meetings I can’t step out of Thx Uri (“Oo-Ree”) C: 949-378-7568 From: Brenden Blanco [mailto:bblanco@...] Sent: Tuesday,

Hi Brendan, Thanks, that’s great. I’ll have a look at that example you mention too. Whereabouts in the code should I look to see which functions are allowable in which bpf program types?

The best source of truth is in the kernel code. The whitelist of functions for networking is: net/core/filter.c: sk_filter_func_proto() tc_cls_act_func_proto() other whitelists are available around

Thanks all for joining today, We had a very interesting session focused entirely on XDP (express data path), a new initiative to improve packet processing performance in the linux kernel. The details

Brenden Blanco <bblanco@...> wrote: I'm doing my usual benchmark driven development. Which means I'm currently benchmarking the lowest RX layer of the drivers and just dropping packets

Hi Brendan, After looking at the xlate tests, I *think* have managed to get my bpf programs attached to my NICS (or rather attached to a qdisc attached to my NICS - as I now understand it).

<iovisor-dev@...> wrote: awesome. that's a great baseline. I think the next step here is to make mlx4 to recycle pages and rx descriptors on its own. Later we can generalize it into

I will heartily acknowledge that the mechanism to attach bpf programs to an interface is non-intuitive. This has been a source of pain for many. The code in https://github.com/iovisor/iomodules is an

On 03/03/2016 08:19 PM, Brenden Blanco via iovisor-dev wrote: [...] > On Thu, Mar 3, 2016 at 5:52 AM, O Mahony, Billy <billy.o.mahony@...> [...] >> #add a filter to accept all eth frame.

Alexei Starovoitov <alexei.starovoitov@...> wrote: Yes, but we might as well start up with making the allocator hacks in mlx4 more generic, when adding recycle. But still keep them locally

Speaking of which, I just opened https://github.com/svinota/pyroute2/pull/223 to add support in pyroute2 upstream. The docstring in that pull request shows an example usage, which I'll also add to a

That's awesome, thanks Brenden!

If you are looking at this you might want to check out what we have today or perhaps your already aware of it. For steering flows to specific queues we have ethtool interface and soon 'tc' will

As promised, the slides are now available here: https://github.com/iovisor/bpf-docs/blob/master/Express_Data_Path.pdf