On Sun, 2016-04-03 at 11:28 +0900, Lorenzo Colitti wrote: > That said, getting BPF to the driver is part of the picture. On the > chipsets we're targeting for APF, we're only seeing 2k-4k of memory > (that's 256-512 BPF instructions) available for filtering code, which > means that BPF might be too large.
That's true, but I think that as far as the userspace API is concerned that shouldn't really be an issue. I think we can compile the BPF into APF, similar to how BPF can be compiled into machine code today. Additionally, I'm not sure we can realistically expect all devices to really implement APF "natively", I think there's a good chance but there's also a possibility of compiling to the native firmware environment, for example. johannes
