On Thu, Feb 04, 2016 at 10:16:56AM +0100, Jiri Pirko wrote: > Wed, Feb 03, 2016 at 10:27:32AM CET, john.fastab...@gmail.com wrote: > > > >Also by adding get_parse_graph and set_parse_graph attributes as > >in my previous flow_api work we can build programmable devices > >and programmatically learn when rules can or can not be loaded > >into the hardware. Again future work. > > > >Any comments/feedback appreciated. > > I like this being thin and elegant solution. However, ~2 years ago when I > pushed openvswitch kernel datapath offload patchset, people were yelling > at me that it is not generic enough solution, that tc has to be able > to use the api (Jamal :)), nftables as well.
I would be glad to join this debate during NetDev 1.1 too. I think we should provide a solution that allows people uses both tc and nftables, this would require a bit of generic infrastructure on top of it so we don't restrict users to one single solution, in other words, we allow the user to select its own poison. > Now this patch is making offload strictly tc-based and nobody seems to > care :) I do. I think that we might try to find some generic middle layer. I agree and I'll be happy to help to push this ahead. Let's try to sit and get together to resolve this. See you soon.
