eiffel-fl

> Thank you @eiffel-fl . I'll integrate the changes and refresh the PR to latest HEAD. You are welcome, ping me when you are ready to get review :D.

I need to get a better understanding how they parse the actual `kconfig` in `libbpf` and I will open a PR to add this feature to what we have now.

> It's fairly straightforward, the only issue I have is that if we parse /proc/config into a map[string]string, it consumes a non-negligible amount of memory that will remain cached for...

Closing as this was addressed in several PR!

I ran again the experiment now what we use `grpc` to get the events stream. The results are under the `grpc/` directory. To conclude, using `grpc` over `exec gadgettracermanager` makes...

> What do you think about reusing the work done in this PR to implement a testing framework, then we can start running the actual tests? For the moment no....

Closing as everything regarding scaling occurs now in https://github.com/inspektor-gadget/inspektor-gadget-scaling.

This gadget and particularly its tracepoints are a pain to handle as they changed over time: https://github.com/inspektor-gadget/inspektor-gadget/blob/ea4bfb16b7a910548289c1fa4d2f2a4ad2237711/pkg/gadgets/top/block-io/tracer/tracer.go#L117-L124 I would not be surprised there is a case like this in both...

> test ig trace exec in addition to kubectl-gadget trace exec (this could be done with a kubectl debug node command) I do not really understand. The whole goal of...

Thank you for the merge!