14/05/2021 12:42, Ferruh Yigit: > On 4/7/2021 11:33 PM, Thomas Monjalon wrote: > > The NICs overview table lists all supported features per driver. > > There was a single row for "Flow API", > > although rte_flow is composed of many items and actions. > > > > The row "Flow API" is replaced with two new tables for items and actions. > > > > Also, since rte_flow is not implemented in all drivers, > > it would be ugly to add empty sections in some files. > > That's why the error message for missing INI section is removed. > > > > The lists are sorted alphabetically. > > The extra files for some VF and vectorized data paths are not filled. > > > > Signed-off-by: Asaf Penso <as...@nvidia.com> > > Signed-off-by: Thomas Monjalon <tho...@monjalon.net> > > <...> > > > +[rte_flow items] > > +eth = Y > > +ipv4 = Y > > +ipv6 = Y > > +pf = Y > > +phy_port = Y > > +port_id = Y > > +tcp = Y > > +udp = Y > > +vf = Y > > +vlan = Y > > +vxlan = Y > > + > > +[rte_flow actions] > > +count = Y > > +drop = Y > > +mark = Y > > +pf = Y > > +phy_port = Y > > +port_id = Y > > +rss = Y > > +vf = Y > > +vxlan_decap = Y > > +vxlan_encap = Y > > Indeed this is a matrix, isn't it, not all flow items support all flow > actions, > but not sure if it is possible to figure out that matrix.
We cannot express combinations and limitations here. It is just showing some basic capabilities without limitations. For more complete description, it must be noted in the guide.
