On Thu, Jun 14, 2018 at 5:55 PM, David Miller <davem@xxxxxxxxxxxxx> wrote: > And guess what? Then millions of possibilities would have been > openned up, rather than just this one special case. > > So, I ask, please see the larger picture. +cc netdev/etc This is perhaps unrelated to the topic at hand, but as someone who's shipped a bunch of devices over the years using the linux kernel forwarding path and needs performance but wants to avoid moving to out of tree userspace offload for all the reasons that you and many others have stated, is the long term vision that the existing kernel forwarding path will transparently take advantage of eBPF (ala bpfilter), or that users will write custom/individualized eBPF forwarding paths for their usecases as necessary? I (and I suspect many others) will start on the latter anyways, I'm just curious whether it's desired/expected that such custom fastpath users will eventually be rolled back into/replaced by a transparent upstream in-kernel equivalent. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
