Simon, Maybe a bit off topic, but I had the impression netronome would support BPF so that filters could be programmed for arbitrary protocols and fields. Is that true? If so, what is the relationship between that functionality and these patches?
Thanks, Tom On Fri, Oct 6, 2017 at 1:21 AM, Simon Horman <simon.hor...@netronome.com> wrote: > Pieter says: > > This series extends flower offload match and action capabilities. It > specifically adds offload capabilities for matching on MPLS, TTL, TOS > and flow label. Furthermore offload capabilities for action have been > expanded to include set ethernet, ipv4, ipv6, tcp and udp headers. > > Pieter Jansen van Vuuren (7): > nfp: add mpls match offloading support > nfp: add IPv4 ttl and tos match offloading support > nfp: add IPv6 ttl and tos match offloading support > nfp: add set ethernet header action flower offload > nfp: add set ipv4 header action flower offload > nfp: add set ipv6 source and destination address > nfp: add set tcp and udp header action flower offload > > drivers/net/ethernet/netronome/nfp/flower/action.c | 245 > +++++++++++++++++++++ > drivers/net/ethernet/netronome/nfp/flower/cmsg.h | 43 ++++ > drivers/net/ethernet/netronome/nfp/flower/match.c | 39 +++- > .../net/ethernet/netronome/nfp/flower/offload.c | 20 +- > 4 files changed, 324 insertions(+), 23 deletions(-) > > -- > 2.1.4 >
