Adjust internal socket API for afpacket / afring to support no-limit BPF filter option #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Restructures the internal API for the socket options into a
struct{}based one (too many options in the method signature anyway) and hence allows exposure of a new option function forafring/afpacketsources:Using this there will be no BPF filtering introduced beyond the flag-based ones (i.e. snaplen, promiscious mode and VLAN ignore mode).
Extra BPF instructions can still be provided in this mode, effectively providing the option to set arbitrary BPF from scratch.
Closes #96