On 10/10/2018 11:23 AM, Shannon Nelson wrote:
> For that matter, lots of features are "default off" until someone configures
> them, and there are lots of features that are only used by a subset of users.
> In this case, we're trying to use something that already exists and arguably
> is broken for the vlan case. Are there some technical reasons why this is
> not a good solution?
Simply code maintenance, and added cost for non vlan users.
Adding extra tests might help your use-case, but is slowing down other cases.
Since the need for new stuff will never end, really eBPF allow for arbitrary
usage,
without the need for review kernel patches and maintaining it for next 10 years.
