<iovisor-dev@...> wrote: You can access through arguments or through "current" task pointer. What exactly you want access on which kprobe? More information will help people to understand

On 04/18/2018 10:03 PM, Jesper Dangaard Brouer via iovisor-dev wrote: [...] > What does bpftool use BFD for? It's used for the prog JIT dump in order to disassemble the instructions.

(Cc. iovisor-dev list) Jesper Dangaard Brouer <brouer@...> wrote: So, I figured out why this happens. What does bpftool use BFD for? I need the BFD lib and include file:

Hi All, Thanks for attending the meeting today. As usual, here are my notes. Cheers, Brenden === Discussion === Alexei - bpf-next queue is quite large, please have patience with delays in clearing

Dear all I'm a student at Paris-VI Univercity and currently I'm working on a project involving eBPF with linux network stack ,and I need some guidence. If we attach the eBPF program to a kprobe

Please join us tomorrow 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

[...] (See below on the detection of it.) Makes sense to have such fallbacks. For the latter, I would just add a BPF_F_STRICT_CONST_VERDICT load flag which e.g. enforces a constant return code in

Daniel Borkmann <daniel@...> wrote: Okay, you want to catch this in dev_ethtool(), that connected the dots for me, thanks. BUT it does feel a little fake and confusing to do this, as the

Ashish, Some comments below. Could you have more details here? Maybe have a skeleton of bpf program to at least see how this helper will be used? A lot of compression happens in the application and

<ping>

Sure, that was perfectly clear. (But at the same time if you extend the ioctl, it's obvious to also add support to actual ethtool cmdline tool.) Not really, that's the front end. ndo_bpf itself is a

Jakub Kicinski <jakub.kicinski@...> wrote: Let's keep thing separate. I'm requesting something really simple. I want the driver to tell me what XDP actions it supports. We/I can

I think Daniel meant for nfp offload. The offload restrictions are quite involved, are we going to be able to express those? This is a bit simpler but reminds me of the TC flower

Victor Julien <lists@...> wrote: The code for querying should not be too difficult. It would likely be similar to how we currently "set"/attach an XDP program, via its BPF file-descriptor

Daniel Borkmann <daniel@...> wrote: Just to be clear: notice as Victor points out[2], they are programmable going though the IOCTL (SIOCETHTOOL) and not using cmdline tools. [2]

I don't really mind if you go via ethtool, as long as we handle this generically from there and e.g. call the dev's ndo_bpf handler such that we keep all the information in one place. This can be a

+1 I would prefer that approach too.

I think if it would use the ioctl ETHTOOL interface it'd be easiest for us, as we already have code for this in place to check for offloading settings. See [1]. Do you have an example of how this is

Extending the ethtools mechanism seems like a clean solution here. It is, by design, a 50% reporting tool and the XDP feature set would be just yet another feature here.

Hi All, Thanks for attending the meeting today. Here are my notes from the call. Cheers, Brenden === Status === Yonghong - Debugging incorrect user stack - fastpath vs slowpath register