I think we have discussed this on matrix.. we should have a table instead of comparing strings.. btw, I think a better approach would be to have a table as an field of skb (e.g., skb.attr) for using __index and __newindex so we can avoid the verification on the top and a second table stored in the lib table itself to access getters and setters CFunctions directly, instead of comparing strings like this. What do you think?

perhaps, a better idea is to just expose getters and setters here and implement the table abstraction in Lua, e.g., skb/attr.lua

perhaps, a better idea is to just expose getters and setters here and implement the table abstraction in Lua, e.g., skb/attr.lua

I agree, this way C side will be straight forward

Added lib/skb/attr.lua to handle the table abstraction

I think we should move this to our common layer, having something like lunatik_ebpf_runtimes.. btw, I was taking a look at the integration branch.. I don't think the header belongs to lib/, lunatik_* should be placed at /, also.. I would rename it to lunatik_ebpf.h, bpf is misnomer IMHO

Working on a fixup for this

I have moved the following to the generic layer till now:

• runtime lookup
• BPF kfunc init and set macros

isn't there anything from attach on XDP and TC that we can generaliza to the lunatik_ebpf layer?